[Kernel-packages] [Bug 1499006] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [gcc: internal compiler error: Bus error (program cc1)]
closing, old issue and not enough information. please provide the preprocessed source and the command line options used if you want to reopen the issue. ** Changed in: gcc-defaults (Ubuntu) Status: Confirmed => Invalid -- 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/1499006 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [gcc: internal compiler error: Bus error (program cc1)] Status in bcmwl package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Bug description: Wireless internet stopped working after update ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 DKMSKernelVersion: 3.13.0-51-generic Date: Wed Sep 23 20:09:41 2015 InstallationDate: Installed on 2014-10-31 (327 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl 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/bcmwl/+bug/1499006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests
** Tags added: sru-20210222 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1821394 Title: vmx tests fail in kvm_unit_tests Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: Confirmed Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test" PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails INFO: Processor supports accessed and dirty flag PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch
[Kernel-packages] [Bug 1918378] Re: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted
** Description changed: + [SRU Justfication] + + BugLink: https://bugs.launchpad.net/bugs/1918378 + + [Impact] + + With headset/mic injected, GNOME Settings does not update record volume + control option to the headset one automatically. + + [Fix] + + https://github.com/CirrusLogic/product- + support/blob/82915ae88a02781b173c83568426722789d74f37/dell/hda/5.10.7/0001 + -ALSA-hda-cirrus-Fix-Headset-Mic-volume-control-name.patch + + [Test Case] + + Tested on affected platform. With the patch, both playback and record + volume control will be updated simultaneously. + + [Where problems could occur] + + Control object name string update only. + + [Other Info] + + This is a follow-up for patchset + https://lists.ubuntu.com/archives/kernel-team/2021-March/117814.html + titled "Cirrus CS8409 HDA bridge/CS42L42 codec support". + + == original bug description == + Steps: 1. With the latest test kernel from Vicamo's PPA as of 3/8 2. Plug in a headset Expected behavior: Input Device should switch to Headset Microphone - Built-in Audio Actual behavior: Input Device remains at Microphone - Built-in Audio and users need to manually switch to correct Input Device for the audio recording via headset to work -- 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/1918378 Title: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justfication] BugLink: https://bugs.launchpad.net/bugs/1918378 [Impact] With headset/mic injected, GNOME Settings does not update record volume control option to the headset one automatically. [Fix] https://github.com/CirrusLogic/product- support/blob/82915ae88a02781b173c83568426722789d74f37/dell/hda/5.10.7/0001 -ALSA-hda-cirrus-Fix-Headset-Mic-volume-control-name.patch [Test Case] Tested on affected platform. With the patch, both playback and record volume control will be updated simultaneously. [Where problems could occur] Control object name string update only. [Other Info] This is a follow-up for patchset https://lists.ubuntu.com/archives/kernel-team/2021-March/117814.html titled "Cirrus CS8409 HDA bridge/CS42L42 codec support". == original bug description == Steps: 1. With the latest test kernel from Vicamo's PPA as of 3/8 2. Plug in a headset Expected behavior: Input Device should switch to Headset Microphone - Built-in Audio Actual behavior: Input Device remains at Microphone - Built-in Audio and users need to manually switch to correct Input Device for the audio recording via headset to work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913410] Re: aws: update Xen hibernation patch set
** Changed in: linux-aws (Ubuntu Groovy) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1913410 Title: aws: update Xen hibernation patch set Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Xenial: New Status in linux-aws source package in Bionic: Triaged Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] Amazon maintains a custom patch to enable hibernation in Xen guests that is not upstream yet. This patch set has been updated in AWS AL2 and we should sync up the patch set in our AWS kernels. [Test case] Tests have been performed (simply doing multiple hibernate/resume cycles) with the new patch set applied and they have shown significant improvement in terms of reliability. [Fix] Backport/apply the new Xen hibernation patch set from AWS AL2. [Regression potential] The patch set is affecting only Xen (in particular the guest code) and only hibernation, so the risk of regressions is restricted to this particular scenario (Xen + hibernation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1913410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1918378] Re: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted
Verified. Going to SRU. ** Attachment added: "pa-info.list.5.10.0-2017-oem.BNI5-DVT2-C1" https://bugs.launchpad.net/bugs/1918378/+attachment/5475328/+files/pa-info.list.5.10.0-2017-oem.BNI5-DVT2-C1 ** Attachment added: "screenshot.5.10.0-2017-oem.BNI5-DVT2-C1.png" https://bugs.launchpad.net/bugs/1918378/+attachment/5475329/+files/screenshot.5.10.0-2017-oem.BNI5-DVT2-C1.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918378 Title: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Steps: 1. With the latest test kernel from Vicamo's PPA as of 3/8 2. Plug in a headset Expected behavior: Input Device should switch to Headset Microphone - Built-in Audio Actual behavior: Input Device remains at Microphone - Built-in Audio and users need to manually switch to correct Input Device for the audio recording via headset to work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
** Changed in: fedora Status: Unknown => Confirmed ** Changed in: fedora Importance: Unknown => Undecided -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. 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, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1
[Kernel-packages] [Bug 1918378] Re: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted
SRU: https://lists.ubuntu.com/archives/kernel- team/2021-March/117900.html (unstable/hirsute/oem-5.10) -- 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/1918378 Title: Cirrus Audio Codec CS8409/CS42L42: Input Device does not switch to headset Mic when a headset is inserted Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Steps: 1. With the latest test kernel from Vicamo's PPA as of 3/8 2. Plug in a headset Expected behavior: Input Device should switch to Headset Microphone - Built-in Audio Actual behavior: Input Device remains at Microphone - Built-in Audio and users need to manually switch to correct Input Device for the audio recording via headset to work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908139] Re: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2
Hi! Are you sure this is not a hardware issue? The reason I believe it is a hardware issue is because I observed my system "drop monitors" on the docking station also under Windows 10 and even while in the UEFI. Lenovo replaced both the motherboard and the docking station (and I updated firmware for both multiple times), however the issue is still present. You say that for you, the problem does not appear under Windows. However, note that (at least in my case) this is a sporadic issue, so it may show up every day or every week or only every one or two months. I know of absolutely no way to predict or even "provoke" this. So are you really sure it is not present for Windows, i. e. have you run the system for MONTHS under Windows and are you sure that your monitors never went off, even for a second or two? I just wanna say that it may be very hard to judge whether this bug is present or not, because it sometimes occurs VERY seldomly. Since I observed it under both Windows 10 and Ubuntu Linux 20.04 LTS and also while in UEFI, I'm pretty sure it is not (only) a software issue. However, I had both motherboard and docking station replaced and it still occurs, suggesting that it may actually be not just a faulty component, but an issue in the actual hardware design, in which case it might affect the entire notebook or even APU series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908139 Title: ThinkPad T14s external display not working on ThinkPad USB-C Dock Gen2 Status in linux package in Ubuntu: Confirmed Bug description: laptop: ThinkPad T14s Gen 1 - AMD Ryzen 7 PRO 4750U docking station: ThinkPad USB-C Dock 2. Gen. external display: NE MultiSync EA275UHD OS: Ubuntu 20.10 - kernel 5.8.0 Plugging the external display into one of the docking station's two DisplayPort connectors leads to the screen resolution changing on the laptop's builtin display and the external display waking up but showing no picture and displaying "no-signal" after a bit. Plugging the external display into the docking station's HDMI connector leads to no visible reaction on either the external nor the builtin display. Plugging the external display into the laptop's builtin HDMI connector works as expected. The external display is recognized and shows an image. I have recorded the output on `dmesg` during the steps mentioned above and inserted explanations using `echo MSG >/dev/kmsg`. The output follows at the end of the message. I believe `ubuntu-bug` should also attach the full log. All above modes of connection work as expected with the same laptop, dock, and display on Windows 10 (installed as dual boot along side Ubuntu). All above modes of connection also work as expected with an older laptop (ThinkPad T470s - Ubuntu 20.04 - kernel 5.4.0), and the same dock and display. This leads me to believe that this is not a hardware issue. The following bug seems related, but seems to have been observed on faulty hardware according to its author. Therefore, I decided to open a separate bug report. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899336 ``` [ 343.372511] plugging DisplayPort into dock port 1 [ 352.666113] [drm] DP Alt mode state on HPD: 1 [ 352.749192] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 352.858482] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.888400] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.892555] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.896719] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.900876] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.905596] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.910323] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 352.914485] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 377.353566] plugged in - no signal [ 396.728970] unplugging [ 403.001418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id: 75] [ 415.576397] unplugged [ 431.500729] plugging DisplayPort into dock port 2 [ 437.607724] [drm] DP Alt mode state on HPD: 1 [ 437.681116] [drm] DM_MST: starting TM on aconnector: 2105a317 [id: 75] [ 437.790303] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.820138] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.824305] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.828462] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.832619] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.837029] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.841984] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 437.846144] [drm] amdgpu_dm_irq_schedule_work FAILED src 9 [ 458.999849] plugged in - no signal [ 465.702949] unplugging [ 476.127418] [drm] DM_MST: stopping TM on aconnector: 2105a317 [id:
[Kernel-packages] [Bug 1906850] Re: aws: xen-netfront: prevent potential error on hibernate
** Changed in: linux-aws (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1906850 Title: aws: xen-netfront: prevent potential error on hibernate Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Released Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] On hibernation xen-netfront is setting the device state on the xenbus to "Closing" and then it's waiting for the backend state to acknowledge that state (with a timeout). However, if the device is already in the state "Closed" this opteration will always hit the timeout, preventing the system to hibernate correctly. [Test case] It is a quite rare condition that can be reproduced hibernating/resuming a Xen instance multiple times. When the problem happens we should in the log a Xen error message like the following: Freezing timed out; the device may become inconsistent state [Fix] If the device is already in the state "Closed", simply tear it down without notifying the Xen backend. [Regression potential] The fix would just prevent aborting hibernation if the netfront device is already in a "Closed" state. The resume callback is forcing the device into the "Initializing" state anyway, basically forcing a reset of the device, so nothing else in the state machine can be potentially broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1906850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
** Bug watch added: Red Hat Bugzilla #1933423 https://bugzilla.redhat.com/show_bug.cgi?id=1933423 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1933423 Importance: Unknown Status: Unknown -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. 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, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions:
[Kernel-packages] [Bug 1913410] Re: aws: update Xen hibernation patch set
** Changed in: linux-aws (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1913410 Title: aws: update Xen hibernation patch set Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Xenial: New Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Fix Committed Bug description: [Impact] Amazon maintains a custom patch to enable hibernation in Xen guests that is not upstream yet. This patch set has been updated in AWS AL2 and we should sync up the patch set in our AWS kernels. [Test case] Tests have been performed (simply doing multiple hibernate/resume cycles) with the new patch set applied and they have shown significant improvement in terms of reliability. [Fix] Backport/apply the new Xen hibernation patch set from AWS AL2. [Regression potential] The patch set is affecting only Xen (in particular the guest code) and only hibernation, so the risk of regressions is restricted to this particular scenario (Xen + hibernation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1913410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918298] Re: Do not make it possible to have multiple nvidia kernel modules installed at the same time
** Description changed: Currently, having different nvidia modules for the same kernel ABI is allowed. For example, both linux-modules-nvidia-450-5.4.0-66-generic and linux-modules-nvidia-460-5.4.0-66-generic can be installed at the same time. This can cause systems to boot using the wrong kernel modules. - We should make sure to have the linux-nvidia ABI packages depend on the - correct userspace, as we already do for the linux-nvidia metapackages. + A simple fix is to use the same dependency on nvidia-kernel- + common-$flavour for the binary (ABI) packages that the linux-modules- + nvidia-$flavour packages already have. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1918298 Title: Do not make it possible to have multiple nvidia kernel modules installed at the same time Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 source package in Bionic: In Progress Status in nvidia-graphics-drivers-460 source package in Focal: In Progress Status in nvidia-graphics-drivers-460 source package in Groovy: In Progress Bug description: Currently, having different nvidia modules for the same kernel ABI is allowed. For example, both linux-modules-nvidia-450-5.4.0-66-generic and linux-modules-nvidia-460-5.4.0-66-generic can be installed at the same time. This can cause systems to boot using the wrong kernel modules. A simple fix is to use the same dependency on nvidia-kernel- common-$flavour for the binary (ABI) packages that the linux-modules- nvidia-$flavour packages already have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1918298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896180] Re: Raspberry Pi HDMI output has thick black borders
Fixed in 21.04 (/boot/firmware/config.txt) ** No longer affects: linux-raspi (Ubuntu) ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1896180 Title: Raspberry Pi HDMI output has thick black borders Status in linux-firmware-raspi2 package in Ubuntu: Fix Released Bug description: Raspberry Pi HDMI output has thick black borders. This appears to be due to some DRM property defaults coming from the kernel. You can fix them in Xorg sessions with: xrandr --output HDMI-1 --set "top margin" 0 xrandr --output HDMI-1 --set "bottom margin" 0 xrandr --output HDMI-1 --set "left margin" 0 xrandr --output HDMI-1 --set "right margin" 0 To work around the issue in Wayland sessions you will need to log into Xorg first, run the above commands, then log out and into Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1896180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
Hi W.R. Irsyad Hamda, Looks like this is the fix: https://github.com/torvalds/linux/commit/216d7aebbfbe1d3361e21c3a97d1607e1c1c48cd It's been added to Bionic: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/sound/pci/hda/patch_realtek.c#n7071 And Focal kernel. https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/tree/sound/pci/hda/patch_realtek.c#n7887 As this bug is quite old, do you still need the fix in 4.4 Xenial? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1651500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902864] Re: aws: update patch to batch hibernate and resume IO requests
** Changed in: linux-aws (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1902864
Title:
aws: update patch to batch hibernate and resume IO requests
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws source package in Focal:
Fix Committed
Status in linux-aws source package in Groovy:
Fix Released
Bug description:
[Impact]
During hibernation and resume the kernel is submitting an individual
IO request for each page of data. In the aws kernel we are using a
custom SAUCE patch to batch IO requests together in order to achieve
better performance.
Recently a patch designed to achieve the same goal has been applied
upstream. This patch has been acknowledged by Amazon and it has shown
a performance improvement.
Moreover, this patch looks much cleaner compared to the custom patch
that we are using and it's upstream, so it makes sense to drop the
previous patch and apply this new one.
[Test case]
Hibernate + resume and measure the time required to perform these
operations.
Performance result reported by Amazon:
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on
a system with limited storage IOPS.
[Fix]
Apply the following upstream commit:
55c4478a8f0ecedc0c1a0c9379380249985c372a ("PM: hibernate: Batch
hibernate and resume IO requests")
Drop the custom aws SAUCE patch:
11c3fa3b29722124f5c9122671983614383686db ("UBUNTU: SAUCE: [aws] PM /
hibernate: Speed up hibernation by batching requests")
[Regression potential]
Upstream patch that allows to drop a custom patch that is doing the
same thing. The only potential regression would be a performance drop,
but according to Amazon's tests and our tests, we didn't notice any
performance regression. Any other kind of regression would be
considered as upstream regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1902864/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913410] Re: aws: update Xen hibernation patch set
** Changed in: linux-aws (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1913410 Title: aws: update Xen hibernation patch set Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Xenial: New Status in linux-aws source package in Bionic: Triaged Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Groovy: Triaged Bug description: [Impact] Amazon maintains a custom patch to enable hibernation in Xen guests that is not upstream yet. This patch set has been updated in AWS AL2 and we should sync up the patch set in our AWS kernels. [Test case] Tests have been performed (simply doing multiple hibernate/resume cycles) with the new patch set applied and they have shown significant improvement in terms of reliability. [Fix] Backport/apply the new Xen hibernation patch set from AWS AL2. [Regression potential] The patch set is affecting only Xen (in particular the guest code) and only hibernation, so the risk of regressions is restricted to this particular scenario (Xen + hibernation). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1913410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
With kernel version 5.6.0-1048-oem, the stack trace looks different, but the problem is still present. [ 4881.023648] [ cut here ] [ 4881.023782] WARNING: CPU: 1 PID: 1113 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1555 dcn20_program_front_end_for_ctx+0x574/0x580 [amdgpu] [ 4881.023783] Modules linked in: bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi nls_iso8859_1 snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_soc_dmic snd_acp3x_rn snd_hda_core snd_acp3x_pdm_dma soundwire_bus tps6598x snd_soc_core snd_compress ac97_bus iwlmvm snd_pcm_dmaengine btusb edac_mce_amd snd_usb_audio btrtl btbcm snd_seq_midi snd_usbmidi_lib btintel kvm_amd mac80211 snd_seq_midi_event joydev snd_hwdep kvm serio_raw input_leds bluetooth libarc4 snd_rawmidi cdc_ether uvcvideo usbnet snd_pcm snd_seq wmi_bmof ecdh_generic videobuf2_vmalloc r8152 videobuf2_memops ecc videobuf2_v4l2 mii videobuf2_common videodev mc thinkpad_acpi ccp iwlwifi snd_seq_device nvram snd_timer snd_rn_pci_acp3x ledtrig_audio snd_pci_acp3x cfg80211 snd ipmi_devintf ipmi_msghandler ucsi_acpi soundcore typec_ucsi i2c_multi_instantiate typec mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic [ 4881.023814] usbhid hid dm_crypt amdgpu rtsx_pci_sdmmc amd_iommu_v2 crct10dif_pclmul gpu_sched i2c_algo_bit crc32_pclmul ghash_clmulni_intel ttm aesni_intel drm_kms_helper crypto_simd cryptd syscopyarea glue_helper sysfillrect sysimgblt fb_sys_fops cec psmouse rc_core i2c_piix4 drm nvme r8169 rtsx_pci nvme_core realtek wmi video i2c_scmi [ 4881.023834] CPU: 1 PID: 1113 Comm: Xorg Tainted: GW 5.6.0-1048-oem #52-Ubuntu [ 4881.023835] Hardware name: LENOVO 20UH001AGE/20UH001AGE, BIOS R1CET61W(1.30 ) 12/21/2020 [ 4881.023951] RIP: 0010:dcn20_program_front_end_for_ctx+0x574/0x580 [amdgpu] [ 4881.023953] Code: c0 74 cb 4c 89 e2 48 89 df e8 f8 36 dd fa eb be 49 8b 45 00 8b 90 e4 01 00 00 85 d2 75 d5 8b 86 4c 04 00 00 85 c0 75 cb eb a4 <0f> 0b e9 14 fb ff ff 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 4881.023954] RSP: 0018:c087019c7810 EFLAGS: 00010202 [ 4881.023956] RAX: a07c6bec5c00 RBX: a07c6bf5 RCX: 0008 [ 4881.023957] RDX: 0001 RSI: a07bd83e RDI: a07c6bf5 [ 4881.023958] RBP: c087019c7848 R08: 0001 R09: [ 4881.023959] R10: 0001 R11: 0004 R12: a07bd83e [ 4881.023960] R13: a07bd83e01b8 R14: a07bd83e01b8 R15: [ 4881.023962] FS: 7f5369b0ca40() GS:a07c7f84() knlGS: [ 4881.023963] CS: 0010 DS: ES: CR0: 80050033 [ 4881.023964] CR2: 55bf4e2329c8 CR3: 0003f6eb2000 CR4: 00340ee0 [ 4881.023965] Call Trace: [ 4881.024076] dc_commit_state_no_check+0x2cd/0x8a0 [amdgpu] [ 4881.024177] dc_commit_state+0x96/0xb0 [amdgpu] [ 4881.024287] amdgpu_dm_atomic_commit_tail+0x344/0x11d0 [amdgpu] [ 4881.024387] ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu] [ 4881.024484] ? dm_read_reg_func+0x40/0xc0 [amdgpu] [ 4881.024576] ? generic_reg_get+0x22/0x40 [amdgpu] [ 4881.024582] ? _cond_resched+0x19/0x30 [ 4881.024658] ? amdgpu_bo_pin_restricted+0x64/0x2b0 [amdgpu] [ 4881.024665] ? ttm_bo_move_to_lru_tail+0x2d/0xc0 [ttm] [ 4881.024668] ? ww_mutex_unlock+0x26/0x30 [ 4881.024673] ? ttm_eu_backoff_reservation+0x49/0x70 [ttm] [ 4881.024748] ? amdgpu_bo_gpu_offset+0x23/0xa0 [amdgpu] [ 4881.024852] ? dm_plane_helper_prepare_fb+0x143/0x270 [amdgpu] [ 4881.024855] ? _cond_resched+0x19/0x30 [ 4881.024858] ? wait_for_completion_timeout+0x3a/0x120 [ 4881.024859] ? _cond_resched+0x19/0x30 [ 4881.024861] ? wait_for_completion_interruptible+0x37/0x160 [ 4881.024877] commit_tail+0x99/0x130 [drm_kms_helper] [ 4881.024887] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper] [ 4881.024990] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] [ 4881.025013] drm_atomic_commit+0x4a/0x50 [drm] [ 4881.025031] drm_atomic_connector_commit_dpms+0xdf/0x100 [drm] [ 4881.025051] drm_mode_obj_set_property_ioctl+0x156/0x2d0 [drm] [ 4881.025070] ? drm_connector_set_obj_prop+0x90/0x90 [drm] [ 4881.025086] drm_connector_property_set_ioctl+0x3b/0x60 [drm] [ 4881.025103] drm_ioctl_kernel+0xae/0xf0 [drm] [ 4881.025119] drm_ioctl+0x234/0x3d0 [drm] [ 4881.025134] ? drm_connector_set_obj_prop+0x90/0x90 [drm] [ 4881.025209] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [ 4881.025213] ksys_ioctl+0x9d/0xd0 [ 4881.025216] __x64_sys_ioctl+0x1a/0x20 [ 4881.025219] do_syscall_64+0x57/0x1b0 [ 4881.025223] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 4881.025225] RIP: 0033:0x7f5369e6c50b [ 4881.025227] 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 [ 4881.025228] RSP:
Re: [Kernel-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
Thank you very much for your kindness, now I have upgraded my ubuntu to focal, but I still don't understand how to solve my problem with the code, because I am just common user of ubuntu, I don't know about coding and manything about ubuntu system, can you help me to solve this ? Pada tanggal Rab, 10 Mar 2021 pukul 15.41 Po-Hsu Lin < 1651...@bugs.launchpad.net> menulis: > Hi W.R. Irsyad Hamda, > > Looks like this is the fix: > > https://github.com/torvalds/linux/commit/216d7aebbfbe1d3361e21c3a97d1607e1c1c48cd > > It's been added to Bionic: > > https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/sound/pci/hda/patch_realtek.c#n7071 > > And Focal kernel. > > https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/tree/sound/pci/hda/patch_realtek.c#n7887 > > As this bug is quite old, > do you still need the fix in 4.4 Xenial? > Thanks > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1651500 > > Title: > [ASUS X441SA] [8086:2284] No sound at all > > Status in alsa-driver package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Incomplete > > Bug description: > 1. Release of ubuntu > Description: Ubuntu 16.04.1 LTS > Release: 16.04 > > 2. version of the package > AlsaMixer v1.1.0 > > > 3. I expect to hear sound from speaker > > 4. I can not any sound from speaker > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 > Uname: Linux 4.4.0-53-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: hamda 1627 F pulseaudio > CurrentDesktop: Unity > Date: Tue Dec 20 22:51:08 2016 > InstallationDate: Installed on 2016-12-15 (5 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: hamda 1627 F pulseaudio > Symptom_Jack: Speaker, Internal > Symptom_Type: No sound at all > Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/08/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X441SA.301 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X441SA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: X441SA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1651500/+subscriptions > -- 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/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No
[Kernel-packages] [Bug 1918330] Re: Bionic update: upstream stable patchset 2021-03-09
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1918330
Title:
Bionic update: upstream stable patchset 2021-03-09
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-03-09
Ported from the following upstream stable releases:
v4.14.219, v4.19.173,
v4.14.220, v4.19.174,
v4.14.221, v4.19.175,
v4.19.176
from git://git.kernel.org/
ACPI: sysfs: Prefer "compatible" modalias
ARM: dts: imx6qdl-gw52xx: fix duplicate regulator naming
wext: fix NULL-ptr-dereference with cfg80211's lack of commit()
net: usb: qmi_wwan: added support for Thales Cinterion PLSx3 modem family
drivers: soc: atmel: Avoid calling at91_soc_init on non AT91 SoCs
drivers: soc: atmel: add null entry at the end of at91_soc_allowed_list[]
KVM: x86/pmu: Fix HW_REF_CPU_CYCLES event pseudo-encoding in
intel_arch_events[]
KVM: x86: get smi pending status correctly
xen: Fix XenStore initialisation for XS_LOCAL
leds: trigger: fix potential deadlock with libata
mt7601u: fix kernel crash unplugging the device
mt7601u: fix rx buffer refcounting
xen-blkfront: allow discard-* nodes to be optional
ARM: imx: build suspend-imx6.S with arm instruction set
netfilter: nft_dynset: add timeout extension to template
xfrm: Fix oops in xfrm_replay_advance_bmp
RDMA/cxgb4: Fix the reported max_recv_sge value
iwlwifi: pcie: use jiffies for memory read spin time limit
iwlwifi: pcie: reschedule in long-running memory reads
mac80211: pause TX while changing interface type
can: dev: prevent potential information leak in can_fill_info()
x86/entry/64/compat: Preserve r8-r11 in int $0x80
x86/entry/64/compat: Fix "x86/entry/64/compat: Preserve r8-r11 in int $0x80"
iommu/vt-d: Gracefully handle DMAR units with no supported address widths
iommu/vt-d: Don't dereference iommu_device if IOMMU_API is not built
NFC: fix resource leak when target index is invalid
NFC: fix possible resource leak
team: protect features update by RCU to avoid deadlock
tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN
kernel: kexec: remove the lock operation of system_transition_mutex
PM: hibernate: flush swap writer after marking
pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()
net/mlx5: Fix memory leak on flow table creation error flow
rxrpc: Fix memory leak in rxrpc_lookup_local
UBUNTU: upstream stable to v4.14.219, v4.19.173
net: dsa: bcm_sf2: put device node before return
ibmvnic: Ensure that CRQ entry read are correctly ordered
ACPI: thermal: Do not call acpi_thermal_check() directly
net_sched: gen_estimator: support large ewma log
phy: cpcap-usb: Fix warning for missing regulator_disable
x86: __always_inline __{rd,wr}msr()
scsi: scsi_transport_srp: Don't block target in failfast state
scsi: libfc: Avoid invoking response handler twice if ep is already completed
mac80211: fix fast-rx encryption check
scsi: ibmvfc: Set default timeout to avoid crash during migration
objtool: Don't fail on missing symbol table
kthread: Extract KTHREAD_IS_PER_CPU
workqueue: Restrict affinity change to rescuer
UBUNTU: upstream stable to v4.14.220, v4.19.174
USB: serial: cp210x: add pid/vid for WSDA-200-USB
USB: serial: cp210x: add new VID/PID for supporting Teraoka AD2000
USB: serial: option: Adding support for Cinterion MV31
arm64: dts: ls1046a: fix dcfg address range
net: lapb: Copy the skb before sending a packet
elfcore: fix building with clang
USB: gadget: legacy: fix an error code in eth_bind()
USB: usblp: don't call usb_set_interface if there's a single alt
usb: dwc2: Fix endpoint direction check in ep_from_windex
ovl: fix dentry leak in ovl_get_redirect
mac80211: fix station rate table updates on assoc
kretprobe: Avoid re-registration of the same kretprobe earlier
xhci: fix bounce buffer usage for non-sg list case
cifs: report error instead of invalid when revalidating a dentry fails
smb3: Fix out-of-bounds bug in SMB2_negotiate()
mmc: core: Limit retries when analyse of SDIO tuples fails
nvme-pci: avoid the deepest sleep state on Kingston A2000 SSDs
ARM:
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** Changed in: kdump-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917918] Re: SRU: Add FUA support for XFS
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917918 Title: SRU: Add FUA support for XFS Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: SRU justification: [Impact] This 4 patch set adds backported support for Forced Unit Access (FUA) on XFS file systems to the 18.04 (Bionic) GA (4.15) kernel. FUA on XFS was added upstream in 4.18. FUA on XFS is important for SQL server work loads. [Test Plan] SQLIOSIM (a package from Microsoft) was used to test performance improvements. Tests were run with an XFS file system mounted on a persistent memory block device (PMEM) partition. Performance metrics were found to exhibit satisfactory improvement gains from the GA kernel. [Where problems could occur] Well, these are patches to file system code. They _could_ cause widespread corruption. However, multiple test passes with sqliosim exhibited no issues. [Other Info] See attached sqliosim.cfg.ini configuration file for test run parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914608] Re: no console during boot on UC20
The list of modules to include in the initrd is not under the kernel's control but ubuntu-core-initramfs. This commit should fix the issue: https://github.com/snapcore/core- initrd/commit/fa088d26aded1a8c8ce9910ccdb81ba99ed976c4 ** Also affects: ubuntu-core-initramfs Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: Confirmed => Invalid ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid ** Changed in: ubuntu-core-initramfs Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914608 Title: no console during boot on UC20 Status in ubuntu-core-initramfs: Fix Released Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Invalid Status in linux-raspi source package in Groovy: Invalid Status in linux-raspi source package in Hirsute: Invalid Bug description: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1914608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] 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 1918466 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/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918471] [NEW] Enable Tegra support for arm64 for NVIDIA Jetson
Public bug reported: Enable CONFIG_ARCH_TEGRA and all Tegra SOC's in the Hirsute arm64 build and add suitable modules to the linux-modules inclusion list. Targeted platform: NVIDIA Jetson AGX Xavier (Jetson family) ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: 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/1918471 Title: Enable Tegra support for arm64 for NVIDIA Jetson Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: Enable CONFIG_ARCH_TEGRA and all Tegra SOC's in the Hirsute arm64 build and add suitable modules to the linux-modules inclusion list. Targeted platform: NVIDIA Jetson AGX Xavier (Jetson family) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Re: Garbage window on external 4k display
apport information ** Tags added: apport-collected focal ** Description changed: - When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock - and dock is connected to a P17 also with a 4k display if you change the - scale to 100% and attempt to run any window based application like a - browser window on the monitor you get periodic pop up areas of garbage. - Happens more if the window is closer to the left side than if in the - middle of the screen. + When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: z 2161 F pulseaudio + /dev/snd/controlC0: z 2161 F pulseaudio + /dev/snd/controlC1: z 2161 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-04 (65 days ago) + InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 + MachineType: LENOVO 20SNZ5GCUS + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash + ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 + RelatedPackageVersions: + linux-restricted-modules-5.6.0-1033-oem N/A + linux-backports-modules-5.6.0-1033-oem N/A + linux-firmware 1.187.6 + Tags: focal + Uname: Linux 5.6.0-1033-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/26/2020 + dmi.bios.vendor: LENOVO + dmi.bios.version: N30ET32W (1.15 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20SNZ5GCUS + 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad P17 Gen 1 + dmi.product.name: 20SNZ5GCUS + dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 + dmi.product.version: ThinkPad P17 Gen 1 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475483/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8
[Kernel-packages] [Bug 1918466] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475484/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] [NEW] Garbage window on external 4k display
Public bug reported: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. ** 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/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: New Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load
Hello, I have the same problem with random freezes. My Ubuntu 20.04.2 LTS (kernel: 5.8.0-44-generic) enjoys crashing randomly without any apparent reason. I have 8 GB of RAM and started with 2 GB of swap when I installed it parallel to my Win 10 (dual boot, they share a harddrive). Recently, I added another hard drive, and today, I have managed to upgrade my swap to 21 GB in total (I "cut off" a part of my second hard drive (which is used as storage) and turned it into a swap partition with priority 1 that is automatically mounted at system start). However, since I have my 21 GB of swap (it is working and shows up in the system monitor window and with swapon -show) the system froze twice: The first time when my machine was simply being idle (I had some firefox windows and an R session open but was AFK, I just realized that it was frozen when I came back) and the second time while I was starting to write this comment (nothing big was running, just a few firefox windows). I think it might be connected to updates since the "Ubuntu-is-loading"-screen took quite a while to disappear when I restarted. Since I suspected LivePatch to cause these freezes I have already disabled LivePatch and check for updates manually on a regular basis. Just before the freeze, I had installed the current update (via the built-in software updater program) and it seemed as if everything was OK with the update. Is there anything to log whatever happens when the system freezes? Because whenever the system freezes all I can do is move the mouse, but clicking and the keyboard don't work. Sometimes I was lucky enough to be able to see the System monitor window, but that didn't indicate any problems (e.g. only 12% of CPU used and less than 1.6 GB of memory). -- 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/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Confirmed Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi
[Summary] This package is safe to include in main. This does need a security review, so I'll assign ubuntu-security List of specific binary packages to be promoted to main: * ftdi-eeprom * libftdi1-2 * libftdi1-dev * libftdi1-doc * libftdipp1-3 * libftdipp1-dev * python3-ftdi1 [Duplication] OK: There is no other package in main providing the same functionality. [Dependencies] OK: All binary dependencies not in main are built by this package [Embedded sources and static linking] OK: none [Security] OK: - no CVEs - does not run a daemon - does not use webkit1,2 - does not use lib*v8 directly - does not open a port - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam, etc) Problems: - Needs review due to the nature of the package - does parse data formats - The FTDI devices can be used for many security relevant purposes. For example, flashrom makes use of FTDI devices in some cases to flash chips. This happens at the highest possible security levels. [Common blockers] OK: - Does not FTBFS - Added foundations-bugs as a bug subscriber - no translation needed - not a python or go package - has test suites that run at build time and as autopkgtest [Packaging red flags] OK: Upstream update history is slow, but not unreasonably so. A new version was released last July [Upstream red flags] OK: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libftdi in Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi Status in flashrom package in Ubuntu: New Status in libftdi package in Ubuntu: Incomplete Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772675] Re: i40e PF reset due to incorrect MDD event
I'm attaching kprobes for the Xenial kernels. These are based on the 4.4.0-203/204 versions. I followed the same test setup for Bionic, as described in the previous comment, and also had similar results. The netdev watchdog seems to take good care of any hung queues, so in the end PF resets will be issued regardless, if necessary. ** Description changed: [Impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the NIC, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [Fix] In the case of MDD events issued for the PF, they are usually the result of a misconfigured TX descriptor and not due to "bad" actions in the VFs. We don't need to issue a reset to the whole NIC, TX hang checks should handle those if necessary. - [Test Case] + [Test Procedure] The bug is unfortunately difficult to reproduce, as there's no detailed documentation on how the i40e firmware detects and raises MDDs. We have seen reports of this happening in Xenial and Bionic, for workloads stressing i40e bonds in LACP mode. Reproducing is easily detected, as the network traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued + + An alternative test procedure makes use of the kprobes attached to the LP bug. The test setup is as follows: + - Create 2 VFs on primary NIC + - Passthrough VF 1 to a Bionic VM + - Start iperf3 client on VM, going through i40evf interface + - Start another iperf3 client on host, going through i40e interface + Both iperf3 clients should be using an external server located on a separate host. By loading the kprobe module while iperf3 is running, we should be able to raise MDDs more consistently. MDD behaviour can change according to firmware version, so we may need to try with different sets of probes. The one with the most consistent results seems to be 'corrupt_tx_desc_addr', which corrupts the cmd_type_offset_bsz field of the last TX descriptor before the NIC is notified of new data. [Regression Potential] Since we're removing resets for the NIC, regressions could show up as issues in connectivity after the MDD events are raised. If the firmware expects the whole NIC to reset, we could see TX/RX hangs and general unresponsiveness in networking. The potential for this should however be fairly low, as this patch has been present since kernel 5.2 and hasn't seen any fixes or regressions upstream. Basic smoke tests also showed that the driver continues working as expected. == [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. ** Attachment added: "probe_tx_xenial.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+attachment/5475473/+files/probe_tx_xenial.c -- 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/1772675 Title: i40e PF reset due to incorrect MDD event Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Bug description: [Impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the NIC, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [Fix] In the case of MDD events issued for the PF, they are usually the result of a misconfigured TX descriptor and not due to "bad" actions in the VFs. We don't need to issue a reset to the whole NIC, TX hang checks should handle those if necessary. [Test Procedure] The bug is unfortunately difficult to reproduce, as there's no detailed documentation on how the i40e firmware detects and raises MDDs. We have seen reports of this happening in Xenial and Bionic, for workloads stressing i40e bonds in LACP mode. Reproducing is easily detected, as the network traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued An alternative test procedure makes use of the kprobes attached to the LP bug. The test setup is as follows: - Create 2 VFs on primary NIC - Passthrough VF 1 to a Bionic VM - Start iperf3 client on VM, going through
[Kernel-packages] [Bug 1772675] Re: i40e PF reset due to incorrect MDD event
** Description changed: [Impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the NIC, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [Fix] In the case of MDD events issued for the PF, they are usually the result of a misconfigured TX descriptor and not due to "bad" actions in the VFs. We don't need to issue a reset to the whole NIC, TX hang checks should handle those if necessary. [Test Procedure] The bug is unfortunately difficult to reproduce, as there's no detailed documentation on how the i40e firmware detects and raises MDDs. We have seen reports of this happening in Xenial and Bionic, for workloads stressing i40e bonds in LACP mode. Reproducing is easily detected, as the network traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued An alternative test procedure makes use of the kprobes attached to the LP bug. The test setup is as follows: - Create 2 VFs on primary NIC - Passthrough VF 1 to a Bionic VM - Start iperf3 client on VM, going through i40evf interface - Start another iperf3 client on host, going through i40e interface Both iperf3 clients should be using an external server located on a separate host. By loading the kprobe module while iperf3 is running, we should be able to raise MDDs more consistently. MDD behaviour can change according to firmware version, so we may need to try with different sets of probes. The one with the most consistent results seems to be 'corrupt_tx_desc_addr', which corrupts the cmd_type_offset_bsz field of the last TX descriptor before the NIC is notified of new data. [Regression Potential] - Since we're removing resets for the NIC, regressions could show up as issues in connectivity after the MDD events are raised. If the firmware expects the whole NIC to reset, we could see TX/RX hangs and general unresponsiveness in networking. The potential for this should however be fairly low, as this patch has been present since kernel 5.2 and hasn't seen any fixes or regressions upstream. Basic smoke tests also showed that the driver continues working as expected. + Since we're removing resets for the NIC, regressions could show up as issues in connectivity after the MDD events are raised. If the firmware expects the whole NIC to reset, we could see TX/RX hangs and general unresponsiveness in networking. The potential for this should however be fairly low, as this patch has been present since kernel 5.2 and hasn't seen any fixes or regressions upstream. Basic smoke tests also showed that the driver continues working as expected, and that necessary PF resets will be issued by the netdev watchdog in case of any hung queues. == [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. -- 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/1772675 Title: i40e PF reset due to incorrect MDD event Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Won't Fix Bug description: [Impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the NIC, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [Fix] In the case of MDD events issued for the PF, they are usually the result of a misconfigured TX descriptor and not due to "bad" actions in the VFs. We don't need to issue a reset to the whole NIC, TX hang checks should handle those if necessary. [Test Procedure] The bug is unfortunately difficult to reproduce, as there's no detailed documentation on how the i40e firmware detects and raises MDDs. We have seen reports of this happening in Xenial and Bionic, for workloads stressing i40e bonds in LACP mode. Reproducing is easily detected, as the network traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued An alternative test procedure makes use of the kprobes attached to the LP bug. The test setup is as follows: - Create 2 VFs on primary NIC -
[Kernel-packages] [Bug 1918471] Re: Enable Tegra support in arm64 for NVIDIA Jetson
** Summary changed: - Enable Tegra support for arm64 for NVIDIA Jetson + Enable Tegra support in arm64 for NVIDIA Jetson -- 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/1918471 Title: Enable Tegra support in arm64 for NVIDIA Jetson Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: Enable CONFIG_ARCH_TEGRA and all Tegra SOC's in the Hirsute arm64 build and add suitable modules to the linux-modules inclusion list. Targeted platform: NVIDIA Jetson AGX Xavier (Jetson family) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
Yes, Ctrl + zooms in and out. If we believe https://www.microsoft.com/accessories/en-ww/products/keyboards/natural- ergonomic-keyboard-4000/b2m-00012 (though my model is not B2M-00012 but 1048) , Microsoft intended the zoom slider on the keyboard to map to zoom in and out, too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475490/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475489/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475485/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475488/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475494/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475491/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475497/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475496/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475492/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475493/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475499/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475498/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475487/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475500/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475486/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918466] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1918466/+attachment/5475495/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Incomplete Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903467] Re: screen freeze in mid-session
Hello, I have the same problem with random freezes. My Ubuntu 20.04.2 LTS (kernel: 5.8.0-44-generic) enjoys crashing randomly without any apparent reason. I have 8 GB of RAM and started with 2 GB of swap when I installed it parallel to my Win 10 (dual boot, they share a harddrive). Recently, I added another hard drive, and today, I have managed to upgrade my swap to 21 GB in total (I "cut off" a part of my second hard drive (which is used as storage) and turned it into a swap partition with priority 1 that is automatically mounted at system start). However, since I have my 21 GB of swap (it is working and shows up in the system monitor window and with swapon -show), the system froze twice: The first time when my machine was simply being idle (I had some firefox windows and an R session open but was AFK, I just realized that it was frozen when I came back) and the second time while I was starting to write another comment about this problem (nothing big was running, just a few firefox windows). So I don't think that swap will solve this problem (at least it obviously didn't solve it for me). I've also got an AMD processor and the same problems, so maybe it is due to the processor? I have always blamed the updates because there was often a note about new updates or a really long start-up time with the "Ubuntu-is-loading"-screen during the restart). Since I suspected LivePatch to cause these freezes, I have already disabled LivePatch and check for updates manually on a regular basis. Just before the freeze, I had installed the current update (via the built-in software updater program), and it seemed as if everything was OK with the update. Is there anything to log whatever happens when the system freezes? Because whenever the system freezes, all I can do is move the mouse, but clicking and the keyboard don't work. Sometimes I was lucky enough to be able to see the System monitor window, but that didn't indicate any problems (e.g., only 12% of CPU used and less than 1.6 GB of memory). And, more importantly, is there any fix yet? -- 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/1903467 Title: screen freeze in mid-session Status in linux package in Ubuntu: Confirmed Bug description: This is a repeat problem to which I attribute to AMD display driver. The problem mostly occur using Firefox with 4 or more tabs open. It's really frustrating to face the prospect of losing data while surfing the net. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: admin-meir 7349 F pulseaudio /dev/snd/controlC0: admin-meir 7349 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Nov 8 15:00:55 2020 InstallationDate: Installed on 2020-09-03 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909647] Re: xfrm_policy.sh in net from ubuntu_kernel_selftests passed with failed sub-cases
** Changed in: linux (Ubuntu Groovy)
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.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1909647
Title:
xfrm_policy.sh in net from ubuntu_kernel_selftests passed with failed
sub-cases
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
Fix Committed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[Impact]
Even with failed cases reported in the xfrm_policy.sh test, the overall
result is still "PASS"
$ sudo ./xfrm_policy.sh
# selftests: net: xfrm_policy.sh
# PASS: policy before exception matches
# FAIL: expected ping to .254 to fail (exceptions)
# PASS: direct policy matches (exceptions)
# PASS: policy matches (exceptions)
# FAIL: expected ping to .254 to fail (exceptions and block policies)
# PASS: direct policy matches (exceptions and block policies)
# PASS: policy matches (exceptions and block policies)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
hresh changes)
# PASS: direct policy matches (exceptions and block policies after hresh
changes)
# PASS: policy matches (exceptions and block policies after hresh changes)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
hthresh change in ns3)
# PASS: direct policy matches (exceptions and block policies after hthresh
change in ns3)
# PASS: policy matches (exceptions and block policies after hthresh change
in ns3)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
htresh change to normal)
# PASS: direct policy matches (exceptions and block policies after htresh
change to normal)
# PASS: policy matches (exceptions and block policies after htresh change to
normal)
# PASS: policies with repeated htresh change
ok 12 selftests: net: xfrm_policy.sh
$ echo $?
0
This is because of the variable "lret" in check_xfrm() is not a local
variable, and it looks like it will override the one in
check_exceptions() thus making the return value become 0 for the
passed test case after the failed one.
[Fix]
* f6e9ceb7a7fc32 (" selftests: xfrm: fix test return value override issue in
xfrm_policy.sh")
Focal kernel got this patch via stable update, and we don't have this
test in Bionic. Only Groovy and OEM-5.6 are affected.
This patch can be cherry-picked into all of the affected kernels.
[Test]
Run the xfrm_policy.sh test, if there is any failed case the final result
will not be 0.
[Regression Potential]
This change is just for testing tools, it's unlikely to affect real kernel
functionality. However it's expected to generate failures in our test report as
it's reflecting the real test result.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1909647/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918228] Re: Fix missing HDMI/DP audio on NVidia card after S3
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918228 Title: Fix missing HDMI/DP audio on NVidia card after S3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: [Impact] NVidia DP/HDMI aduio disappears after S3. This is a regression introduced by LP: #1867704. [Fix] Update ELD properly so jack status is correctly reported. [Test] Perform S3 and open Sound Settings. With the fix applied, the DP/HDMI audio is always present after S3. [Where problems could occur] This series changes how ELD gets update. So if device depends on the original behavior, jack status could be wrong after this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772675] Re: i40e PF reset due to incorrect MDD event
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772675 Title: i40e PF reset due to incorrect MDD event Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Bug description: [Impact] The i40e driver sometimes causes a "malicious device" event that the firmware detects, which causes the firmware to reset the NIC, causing an interruption in the network connection - which can cause further problems, e.g. if the interface is in a bond; the reset will at least cause a temporary interruption in network traffic. [Fix] In the case of MDD events issued for the PF, they are usually the result of a misconfigured TX descriptor and not due to "bad" actions in the VFs. We don't need to issue a reset to the whole NIC, TX hang checks should handle those if necessary. [Test Procedure] The bug is unfortunately difficult to reproduce, as there's no detailed documentation on how the i40e firmware detects and raises MDDs. We have seen reports of this happening in Xenial and Bionic, for workloads stressing i40e bonds in LACP mode. Reproducing is easily detected, as the network traffic will be interrupted and the system logs will contain a message like: i40e :02:00.1: TX driver issue detected, PF reset issued An alternative test procedure makes use of the kprobes attached to the LP bug. The test setup is as follows: - Create 2 VFs on primary NIC - Passthrough VF 1 to a Bionic VM - Start iperf3 client on VM, going through i40evf interface - Start another iperf3 client on host, going through i40e interface Both iperf3 clients should be using an external server located on a separate host. By loading the kprobe module while iperf3 is running, we should be able to raise MDDs more consistently. MDD behaviour can change according to firmware version, so we may need to try with different sets of probes. The one with the most consistent results seems to be 'corrupt_tx_desc_addr', which corrupts the cmd_type_offset_bsz field of the last TX descriptor before the NIC is notified of new data. [Regression Potential] Since we're removing resets for the NIC, regressions could show up as issues in connectivity after the MDD events are raised. If the firmware expects the whole NIC to reset, we could see TX/RX hangs and general unresponsiveness in networking. The potential for this should however be fairly low, as this patch has been present since kernel 5.2 and hasn't seen any fixes or regressions upstream. Basic smoke tests also showed that the driver continues working as expected, and that necessary PF resets will be issued by the netdev watchdog in case of any hung queues. == [original description] This is a continuation from bug 1713553 and then bug 1723127; a patch was added in the first bug and then the second bug, to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. See bug 1713553 and bug 1723127 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918516] [NEW] Groovy update: upstream stable patchset 2021-03-10
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-03-10 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Groovy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918516 Title: Groovy update: upstream stable patchset 2021-03-10 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-03-10 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1903467] Re: screen freeze in mid-session
21 GB for swap alone is way too much. Normally the size should be twice the size of the memory - or in your case 2x8 =16GB. If you can replace your hard drive to SSD one the system will run much faster, Finally. I used to run my laptops with dual-boot. No longer. I simply replaced the Win10 on my new DELL Insiron 3180 with ubuntu-only laptop. (With backup / Restore capabilities - you can restore it back to Win10 anytime) As for the freeze. I religiously update my ubuntu - particularly for security updates. Also, try to change the suspend time to a longer period (30min) and say if helps. good luck On Wednesday, March 10, 2021, 1:40:55 PM PST, d0bby <1903...@bugs.launchpad.net> wrote: Hello, I have the same problem with random freezes. My Ubuntu 20.04.2 LTS (kernel: 5.8.0-44-generic) enjoys crashing randomly without any apparent reason. I have 8 GB of RAM and started with 2 GB of swap when I installed it parallel to my Win 10 (dual boot, they share a harddrive). Recently, I added another hard drive, and today, I have managed to upgrade my swap to 21 GB in total (I "cut off" a part of my second hard drive (which is used as storage) and turned it into a swap partition with priority 1 that is automatically mounted at system start). However, since I have my 21 GB of swap (it is working and shows up in the system monitor window and with swapon -show), the system froze twice: The first time when my machine was simply being idle (I had some firefox windows and an R session open but was AFK, I just realized that it was frozen when I came back) and the second time while I was starting to write another comment about this problem (nothing big was running, just a few firefox windows). So I don't think that swap will solve this problem (at least it obviously didn't solve it for me). I've also got an AMD processor and the same problems, so maybe it is due to the processor? I have always blamed the updates because there was often a note about new updates or a really long start-up time with the "Ubuntu-is-loading"-screen during the restart). Since I suspected LivePatch to cause these freezes, I have already disabled LivePatch and check for updates manually on a regular basis. Just before the freeze, I had installed the current update (via the built-in software updater program), and it seemed as if everything was OK with the update. Is there anything to log whatever happens when the system freezes? Because whenever the system freezes, all I can do is move the mouse, but clicking and the keyboard don't work. Sometimes I was lucky enough to be able to see the System monitor window, but that didn't indicate any problems (e.g., only 12% of CPU used and less than 1.6 GB of memory). And, more importantly, is there any fix yet? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1903467 Title: screen freeze in mid-session Status in linux package in Ubuntu: Confirmed Bug description: This is a repeat problem to which I attribute to AMD display driver. The problem mostly occur using Firefox with 4 or more tabs open. It's really frustrating to face the prospect of losing data while surfing the net. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: admin-meir 7349 F pulseaudio /dev/snd/controlC0: admin-meir 7349 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Nov 8 15:00:55 2020 InstallationDate: Installed on 2020-09-03 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware 1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E
[Kernel-packages] [Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
I also looked at this and compared with older kernels. This test has never progressed past the "Kretprobe dynamic event with maxactive" test on 5.8, but it has on 5.4: ``` 18:41:31 DEBUG| [stdout] # [43] Kprobe event parser error log check [PASS] 18:41:32 DEBUG| [stdout] # [44] Kretprobe dynamic event with arguments [PASS] 18:41:33 DEBUG| [stdout] # [45] Kretprobe dynamic event with maxactive [PASS] 18:41:49 DEBUG| [stdout] # [46] Register/unregister many kprobe events [PASS] 18:41:49 DEBUG| [stdout] # [47] Kprobe dynamic event - adding and removing [PASS] 18:41:50 DEBUG| [stdout] # [48] Uprobe event parser error log check [PASS] 18:41:50 DEBUG| [stdout] # [49] test for the preemptirqsoff tracer [UNSUPPORTED] 18:42:32 DEBUG| [stdout] # [50] Meta-selftest [PASS] ``` I suspect that next test is causing a hang and ssh dies. The autopkgtest infrastructure sees this and tries to provide some debugging info (the console log and vm details). -- 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/1918226 Title: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Bug description: Testing failed on: arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/linux/20210308_234307_e716b@/log.gz Looks to be a flaky test with this error occurring frequently. This is not a regression. Found a previously reported (expired) bug with the same error: https://launchpad.net/bugs/1549425 [ 6606.751232] audit: backlog limit Creating nova instance adt-groovy-arm64-linux-20210308-143145 from image adt/ubuntu-groovy-arm64-server-20210308.img (UUID 1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)... Creating nova instance adt-groovy-arm64-linux-20210308-143145 from image adt/ubuntu-groovy-arm64-server-20210308.img (UUID 1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)... autopkgtest [23:42:55]: ERROR: testbed failure: testbed auxverb failed with exit code 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918516] Re: Groovy update: upstream stable patchset 2021-03-10
** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-03-10 -upstream stable patchset 2021-03-10 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.4.94, v5.10.12, + v5.4.95, v5.10.13 + + from git://git.kernel.org/ + + gpio: mvebu: fix pwm .get_state period calculation + HID: wacom: Correct NULL dereference on AES pen proximity + media: v4l2-subdev.h: BIT() is not available in userspace + RDMA/vmw_pvrdma: Fix network_hdr_type reported in WC + kernel/io_uring: cancel io_uring before task works + io_uring: dont kill fasync under completion_lock + objtool: Don't fail on missing symbol table + mm/page_alloc: add a missing mm_page_alloc_zone_locked() tracepoint + mm: fix a race on nr_swap_pages + tools: Factor HOSTCC, HOSTLD, HOSTAR definitions + UBUNTU: upstream stable to v5.4.94, v5.10.12 + iwlwifi: provide gso_type to GSO packets + tty: avoid using vfs_iocb_iter_write() for redirected console writes + ACPI: sysfs: Prefer "compatible" modalias + kernel: kexec: remove the lock operation of system_transition_mutex + ALSA: hda/realtek: Enable headset of ASUS B1400CEPE with ALC256 + ALSA: hda/via: Apply the workaround generically for Clevo machines + parisc: Enable -mlong-calls gcc option by default when !CONFIG_MODULES + media: cec: add stm32 driver + media: hantro: Fix reset_raw_fmt initialization + media: rc: fix timeout handling after switch to microsecond durations + media: rc: ite-cir: fix min_timeout calculation + media: rc: ensure that uevent can be read directly after rc device register + ARM: dts: tbs2910: rename MMC node aliases + ARM: dts: ux500: Reserve memory carveouts + ARM: dts: imx6qdl-gw52xx: fix duplicate regulator naming + wext: fix NULL-ptr-dereference with cfg80211's lack of commit() + ASoC: AMD Renoir - refine DMI entries for some Lenovo products + drm/i915: Always flush the active worker before returning from the wait + drm/i915/gt: Always try to reserve GGTT address 0x0 + drivers/nouveau/kms/nv50-: Reject format modifiers for cursor planes + net: usb: qmi_wwan: added support for Thales Cinterion PLSx3 modem family + s390: uv: Fix sysfs max number of VCPUs reporting + s390/vfio-ap: No need to disable IRQ after queue reset + PM: hibernate: flush swap writer after marking + x86/entry: Emit a symbol for register restoring thunk + efi/apple-properties: Reinstate support for boolean properties + drivers: soc: atmel: Avoid calling at91_soc_init on non AT91 SoCs + drivers: soc: atmel: add null entry at the end of at91_soc_allowed_list[] + btrfs: fix possible free space tree corruption with online conversion + KVM: x86/pmu: Fix HW_REF_CPU_CYCLES event pseudo-encoding in intel_arch_events[] + KVM: x86/pmu: Fix UBSAN shift-out-of-bounds warning in intel_pmu_refresh() + KVM: nVMX: Sync unsync'd vmcs02 state to vmcs12 on migration + KVM: x86: get smi pending status correctly + KVM: Forbid the use of tagged userspace addresses for memslots + xen: Fix XenStore initialisation for XS_LOCAL + leds: trigger: fix potential deadlock with libata + arm64: dts: broadcom: Fix USB DMA address translation for Stingray + mt7601u: fix kernel crash unplugging the device + mt7601u: fix rx buffer refcounting + iwlwifi: Fix IWL_SUBDEVICE_NO_160 macro to use the correct bit. + drm/i915/gt: Clear CACHE_MODE prior to clearing residuals + drm/i915/pmu: Don't grab wakeref when enabling events + net/mlx5e: Fix IPSEC stats + ARM: dts: imx6qdl-kontron-samx6i: fix pwms for lcd-backlight + drm/nouveau/svm: fail NOUVEAU_SVM_INIT ioctl on unsupported devices + drm/i915: Check for all subplatform bits + drm/i915/selftest: Fix potential memory leak + uapi: fix big endian definition of ipv6_rpl_sr_hdr + KVM: Documentation: Fix spec for KVM_CAP_ENABLE_CAP_VM + tee: optee: replace might_sleep with cond_resched + xen-blkfront: allow discard-* nodes to be optional + clk: mmp2: fix build without CONFIG_PM + clk: qcom: gcc-sm250: Use floor ops for sdcc clks + ARM: imx: build suspend-imx6.S
[Kernel-packages] [Bug 1918466] Re: Garbage window on external 4k display
** 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/1918466 Title: Garbage window on external 4k display Status in linux package in Ubuntu: Confirmed Bug description: When connecting a 4k monitor to the DP port of a Lenovo TBT3 Gen2 dock and dock is connected to a P17 also with a 4k display if you change the scale to 100% and attempt to run any window based application like a browser window on the monitor you get periodic pop up areas of garbage. Happens more if the window is closer to the left side than if in the middle of the screen. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: z 2161 F pulseaudio /dev/snd/controlC0: z 2161 F pulseaudio /dev/snd/controlC1: z 2161 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-04 (65 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 MachineType: LENOVO 20SNZ5GCUS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1033-oem root=UUID=79aeb320-7842-4144-b3d7-30a10d0f8d0e ro quiet splash ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1033-oem N/A linux-backports-modules-5.6.0-1033-oem N/A linux-firmware 1.187.6 Tags: focal Uname: Linux 5.6.0-1033-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N30ET32W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SNZ5GCUS 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.modalias: dmi:bvnLENOVO:bvrN30ET32W(1.15):bd10/26/2020:svnLENOVO:pn20SNZ5GCUS:pvrThinkPadP17Gen1:rvnLENOVO:rn20SNZ5GCUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P17 Gen 1 dmi.product.name: 20SNZ5GCUS dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1 dmi.product.version: ThinkPad P17 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
my version is 5.4.0-66-generic this is complete text that I got after typed the command Linux hamda 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Pada tanggal Kam, 11 Mar 2021 pukul 09.35 Po-Hsu Lin < 1651...@bugs.launchpad.net> menulis: > Hello, > thanks for the quick reply, do you still experiencing this issue with > Focal? > > This piece of code has landed on Focal 5.4 kernel since 5.4.0-8.11 (you > can check yours with `uname -a` command in a terminal) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1651500 > > Title: > [ASUS X441SA] [8086:2284] No sound at all > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > 1. Release of ubuntu > Description: Ubuntu 16.04.1 LTS > Release: 16.04 > > 2. version of the package > AlsaMixer v1.1.0 > > > 3. I expect to hear sound from speaker > > 4. I can not any sound from speaker > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 > Uname: Linux 4.4.0-53-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: hamda 1627 F pulseaudio > CurrentDesktop: Unity > Date: Tue Dec 20 22:51:08 2016 > InstallationDate: Installed on 2016-12-15 (5 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: hamda 1627 F pulseaudio > Symptom_Jack: Speaker, Internal > Symptom_Type: No sound at all > Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/08/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X441SA.301 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X441SA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: X441SA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions > -- 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/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1805099] Re: nvidia: module verification failed: signature and/or required key missing - tainting kernel
I asked a question at https://answers.launchpad.net/ubuntu/+question/695930 , so yes, it is a bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805099 Title: nvidia: module verification failed: signature and/or required key missing - tainting kernel Status in linux package in Ubuntu: Confirmed Bug description: [2.339868] nvidia: loading out-of-tree module taints kernel. [2.339881] nvidia: module license 'NVIDIA' taints kernel. [2.339882] Disabling lock debugging due to kernel taint [2.344554] usb 1-3: new high-speed USB device number 3 using xhci_hcd [2.354676] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.368949] nvidia-nvlink: Nvlink Core is being initialized, major device number 239 [2.369522] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [2.369735] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts) [2.386968] PKCS#7 signature not signed with a trusted key [2.390444] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.87 Tue Aug 21 16:16:14 PDT 2018 [2.391646] PKCS#7 signature not signed with a trusted key [2.394094] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver [2.394098] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on minor 0 cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 55 model name : Intel(R) Pentium(R) CPU J2900 @ 2.41GHz stepping: 8 microcode : 0x837 cpu MHz : 1332.996 cache size : 1024 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat bugs: cpu_meltdown spectre_v1 spectre_v2 bogomips: 4831.40 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 55 model name : Intel(R) Pentium(R) CPU J2900 @ 2.41GHz stepping: 8 microcode : 0x837 cpu MHz : 1332.896 cache size : 1024 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat bugs: cpu_meltdown spectre_v1 spectre_v2 bogomips: 4831.40 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 55 model name : Intel(R) Pentium(R) CPU J2900 @ 2.41GHz stepping: 8 microcode : 0x837 cpu MHz : 1332.828 cache size : 1024 KB physical id : 0 siblings: 4 core id : 2 cpu cores : 4 apicid : 4 initial apicid : 4 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp tpr_shadow vnmi
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic
** Tags added: hwe-5.8 sru-20210222 -- 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/1836694 Title: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** Tags added: hwe-5.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: Confirmed Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
** Tags added: hwe-5.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-aws source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux-aws source package in Eoan:
New
Bug description:
startup='Wed May 22 08:02:52 2019'
getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup
getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4
canonical name ("curly.maas") doesn't match hostname ("curly")
getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic
lookup ("curly") returns -5 ("No address associated with hostname")
tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 02:57 seq
crw-rw 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Wed May 22 08:04:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-50-generic N/A
linux-backports-modules-4.15.0-50-generic N/A
linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails
** Tags added: hwe-5.8 -- 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/1853610 Title: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Series: E Problem: commands test in ubuntu_ltp fails on E, test cases listed below: * mkfs01_ext3_sh * mkfs01_ext4_sh * nm01_sh startup='Fri Dec 6 02:30:45 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 startup='Fri Dec 6 02:30:52 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext4_sh stime=1575599452 dur=2 exit=exited stat=1 core=no cu=4 cs=1 startup='Fri Dec 6 02:28:44 2019' nm01 1 TINFO: timeout per run is 0h 5m 0s nm01 1 TPASS: nm -f posix -A lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 1 TPASS: nm -f posix -A dir/lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 2 TPASS: nm -f posix -g /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 2 TPASS: Got only external symbols with -g nm01 3 TPASS: nm -f posix -t o /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 3 TPASS: Got an octal symbol values with -f nm01 4 TPASS: nm -f sysv /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 4 TPASS: Got SysV format with -f sysv nm01 5 TPASS: nm -f bsd /opt/ltp/testcases/data/nm01/f1 > nm_bsd.out passed as expected nm01 5 TPASS: nm -f posix /opt/ltp/testcases/data/nm01/f1 > nm_posix.out passed as expected nm01 5 TFAIL: Got wrong format with -f bsd 3dc8 d _DYNAMIC 3fb8 d _GLOBAL_OFFSET_TABLE_ 2000 R _IO_stdin_used w _ITM_deregisterTMCloneTable w _ITM_registerTMCloneTable 2154 r __FRAME_END__ 2010 r __GNU_EH_FRAME_HDR 4010 D __TMC_END__ 4010 B __bss_start w __cxa_finalize@@GLIBC_2.2.5 4000 D __data_start 1120 t __do_global_dtors_aux 3dc0 d __do_global_dtors_aux_fini_array_entry 4008 D __dso_handle 3db8 d __frame_dummy_init_array_entry w __gmon_start__ 3dc0 d __init_array_end 3db8 d __init_array_start 11e0 T __libc_csu_fini 1170 T __libc_csu_init U __libc_start_main@@GLIBC_2.2.5 4010 D _edata 4018 B _end 11e8 T _fini 1000 t _init 1080 T _start 4010 b completed.8055 4000 W data_start 10b0 t deregister_tm_clones 1160 t frame_dummy 1060 T main U puts@@GLIBC_2.2.5 10e0 t register_tm_clones nm01 6 TPASS: nm -f sysv -u /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 6 TPASS: Got undefined symbols with -u nm01 7 TPASS: nm -s /opt/ltp/testcases/data/nm01/lib.a > nm.out passed as expected nm01 7 TPASS: Got index with -s nm01 8 TINFO: AppArmor enabled, this may affect test results nm01 8 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) nm01 8 TINFO: loaded AppArmor profiles: none Summary: passed 16 failed 1 skipped 0 warnings 0 tag=nm01_sh stime=1575599324 dur=0 exit=exited stat=1 core=no cu=3 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853610/+subscriptions --
[Kernel-packages] [Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
Finding failure on Focal/hwe-5.8 5.8.0-45.51~20.04.1 generic-64k, hose: starmie-kernel Though it's instead "ERROR: kernel tainted flag != 0: 512" 1. 03/11 04:40:30 INFO |ubuntu_boo:0042| Checking kernel tainted flags in /proc/sys/kernel/tainted 2. 03/11 04:40:30 INFO |ubuntu_boo:0046| ERROR: kernel tainted flag != 0: 512 3. 03/11 04:40:30 INFO |ubuntu_boo:0046| 4. 03/11 04:40:30 ERROR| test:0414| Exception escaping from test: 5. Traceback (most recent call last): 6. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec 7. _call_test_function(self.execute, *p_args, **p_dargs) 8. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function 9. return func(*args, **dargs) 10. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute 11. postprocess_profiled_run, args, dargs) 12. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once 13. self.run_once(*args, **dargs) 14. File "/home/ubuntu/autotest/client/tests/ubuntu_boot/ubuntu_boot.py", line 59, in run_once 15. raise error.TestFail() 16. TestFail ** Tags added: 5.8 hwe-5.8 -- 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/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Issue found on node grumman, this is not a regression. The kernel_tainted check reports a non-zero flag 2048, this means "workaround for bug in platform firmware applied" log_check reports WARNINGs found in the dmesg: 10. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 7.852005] WARNING: CPU: 0 PID: 179 at /build/linux-0dlxvs/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 11. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 5.387292] WARNING: CPU: 0 PID: 181 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 12. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 6.039705] WARNING: CPU: 0 PID: 4 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
If you are still experiencing the problem in focal, please just open a Terminal window and run this command: apport-collect 1651500 That should send us the fresh information we need. ** No longer affects: alsa-driver (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/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917674] [NEW] [amdgpu] kernel crash when resuming from automatic suspension to RAM
You have been subscribed to a public bug: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal -- [amdgpu] kernel crash when resuming from automatic suspension to RAM https://bugs.launchpad.net/bugs/1917674 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 1917674] Re: [amdgpu] kernel crash when resuming from automatic suspension to RAM
Yes the problem appears to be crashes in the amdgpu kernel driver so please try some other kernel versions and tell us which have or don't have the same bug: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Summary changed: - Freeze when resuming from automatic suspension to RAM + [amdgpu] kernel crash when resuming from automatic suspension to RAM ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Tags added: amdgpu ** Tags added: resume suspend-resume -- 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/1917674 Title: [amdgpu] kernel crash when resuming from automatic suspension to RAM Status in linux package in Ubuntu: Incomplete Bug description: Automatic suspension causes the system to freeze on resume. This doesn't happen if I suspend it manually by opening the system menu and pressing the suspend button. Suspension works flawlessly when it is triggered manually. When the system resumes from automatic suspension, the lock screen is visible but does not respond. It's frozen. A notification says something like "system will suspend shortly due to inactivity". It never goes away. The keyboard responds during this (at least for a while). The CAPS LOCK LED turns on and off as I press it (with no delay). Sometimes I can even switch to another TTY and kill the X server, which is why I'm reporting it against gnome-shell. When switching TTY is impossible, I use the "REISUB" combination to shut down. Either way, I always lose the running session. This is reproducible about 60% of the time. Eventually I ended up disabling it and relying only on manual suspension. # Additional information: 1) Ubuntu 20.04.2 LTS / Release: 20.04 2) gnome-shell 3.36.4-1ubuntu1~20.04.2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 16:56:01 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-31 (31 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879328] Re: ubuntu_kvm_unit_test failed to build on Focal PowerPC
** Tags added: 5.8 hwe-5.8 -- 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/1879328 Title: ubuntu_kvm_unit_test failed to build on Focal PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Compilation failed with: ld: ld: powerpc/selftest.elfpowerpc/spapr_hcall.elf: error: PHDR segment not covered by LOAD segment: error: PHDR segment not covered by LOAD segment ld: powerpc/rtas.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/emulator.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/sprs.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/tm.elf: error: PHDR segment not covered by LOAD segment Full build log: $ sudo make -j156 standalone gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.selftest.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/selftest.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/selftest.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.spapr_hcall.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/spapr_hcall.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/spapr_hcall.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.rtas.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/rtas.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/rtas.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.emulator.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/emulator.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/emulator.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.tm.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/tm.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/tm.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I
[Kernel-packages] [Bug 1886912] [NEW] DELL M3800 Touchscreen not working after login with fractional scaling.
You have been subscribed to a public bug: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bot-comment focal wayland-session xrandr-scaling -- DELL M3800 Touchscreen not working after login with fractional scaling. https://bugs.launchpad.net/bugs/1886912 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware 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 1886912] Re: DELL M3800 Touchscreen not working after login (but works if fwupd is removed)
> fwupd It sounds like it might be part of the reason that this commit went in upstream: https://github.com/fwupd/fwupd/commit/277347688427fd1bf68d68d8d8788bf67d42e01c If you want to keep fwupd on your system, for now you can instead add synaptics_rmi into the BlacklistPlugins= or DsiabledPlugins= field of /etc/fwupd/daemon.conf -- 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/1886912 Title: DELL M3800 Touchscreen not working after login (but works if fwupd is removed) Status in fwupd package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1886912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login (but works if fwupd is removed)
Fixed for 1_4_X: https://github.com/fwupd/fwupd/commit/42e01911cd683a659367e453737d49a50ce6308f Fixed for 1_3_X: https://github.com/fwupd/fwupd/commit/67596cb1d8e5b8177de15ee29b53a058857c3056 ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** No longer affects: linux-firmware (Ubuntu) ** Also affects: fwupd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Changed in: fwupd (Ubuntu Focal) Status: New => Triaged ** Changed in: fwupd (Ubuntu Groovy) Status: New => Triaged ** Changed in: fwupd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: fwupd (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: fwupd (Ubuntu Groovy) Importance: Low => Medium -- 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/1886912 Title: DELL M3800 Touchscreen not working after login (but works if fwupd is removed) Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Focal: Triaged Status in fwupd source package in Groovy: Triaged Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1886912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829983] Re: memcg_stat from controllers test suite in LTP failed
** Tags added: hwe-5.8 ** Tags added: sru-20210222 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829983 Title: memcg_stat from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: memcg_stat_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_stat_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 1 TINFO: Running memcg_process --shm -k 3 -s 135168 memcg_stat_test 1 TINFO: Warming up pid: 31352 memcg_stat_test 1 TINFO: Process is still here after warm up: 31352 memcg_stat_test 1 TPASS: cache is 135168 as expected memcg_stat_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_stat_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 2 TINFO: Running memcg_process --mmap-file -s 135168 memcg_stat_test 2 TINFO: Warming up pid: 31380 memcg_stat_test 2 TINFO: Process is still here after warm up: 31380 memcg_stat_test 2 TPASS: mapped_file is 135168 as expected memcg_stat_test 3 TINFO: Starting test 3 sh: echo: I/O error memcg_stat_test 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 3 TINFO: Running memcg_process --mmap-lock1 -s 4096 memcg_stat_test 3 TINFO: Warming up pid: 31409 memcg_stat_test 3 TINFO: Process is still here after warm up: 31409 memcg_stat_test 3 TPASS: unevictable is 4096 as expected memcg_stat_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_stat_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 4 TINFO: Running memcg_process --mmap-lock2 -s 4096 memcg_stat_test 4 TINFO: Warming up pid: 31434 memcg_stat_test 4 TINFO: Process is still here after warm up: 31434 memcg_stat_test 4 TPASS: unevictable is 4096 as expected memcg_stat_test 5 TINFO: Starting test 5 sh: echo: I/O error memcg_stat_test 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 5 TPASS: hierarchical_memory_limit is 4096 as expected memcg_stat_test 6 TINFO: Starting test 6 sh: echo: I/O error memcg_stat_test 6 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed sh: echo: I/O error memcg_stat_test 6 TFAIL: hierarchical_memory_limit is 4096, 8192 expected memcg_stat_test 7 TINFO: Starting test 7 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled memcg_stat_test 7 TINFO: Starting test 8 sh: echo: I/O error memcg_stat_test 7 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_stat_test 7 TCONF: mem+swap is not enabled tag=memcg_stat stime=1558504742 dur=4 exit=exited stat=33 core=no cu=16 cs=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU
[Kernel-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
Hello, thanks for the quick reply, do you still experiencing this issue with Focal? This piece of code has landed on Focal 5.4 kernel since 5.4.0-8.11 (you can check yours with `uname -a` command in a terminal) -- 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/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886912] Re: DELL M3800 Touchscreen not working after login with fractional scaling.
** Package changed: xserver-xorg-input-libinput (Ubuntu) => linux- firmware (Ubuntu) ** Package changed: mutter (Ubuntu) => fwupd (Ubuntu) ** Summary changed: - DELL M3800 Touchscreen not working after login with fractional scaling. + DELL M3800 Touchscreen not working after login ** Tags removed: xrandr-scaling ** No longer affects: libinput (Ubuntu) ** Summary changed: - DELL M3800 Touchscreen not working after login + DELL M3800 Touchscreen not working after login (but works if fwupd is removed) -- 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/1886912 Title: DELL M3800 Touchscreen not working after login (but works if fwupd is removed) Status in fwupd package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Hello, I have freshly installed Ubuntu 20.04 and have a bug on my M3800. The touchscreen is working good on login screen bug after I enter my credentials and the gnome session open I can't use it. I'm on a dual boot computer and all is working well on Windows 10. How can I help you to track this bug and solve it ? Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1886912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918582] [NEW] nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build
Public bug reported: I changed to use the nvidia-driver-460(proprietary,tested) and this error keep popping up everytime i logged in ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 (not installed) ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-44-generic Date: Tue Mar 9 23:41:30 2021 DuplicateSignature: dkms:nvidia-kernel-source-450:450.51.05-0ubuntu1:/var/lib/dkms/nvidia/450.51.05/build/common/inc/nv-linux.h:508:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2021-02-22 (16 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 450.51.05-0ubuntu1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1918582 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: I changed to use the nvidia-driver-460(proprietary,tested) and this error keep popping up everytime i logged in ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 (not installed) ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-44-generic Date: Tue Mar 9 23:41:30 2021 DuplicateSignature: dkms:nvidia-kernel-source-450:450.51.05-0ubuntu1:/var/lib/dkms/nvidia/450.51.05/build/common/inc/nv-linux.h:508:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2021-02-22 (16 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 450.51.05-0ubuntu1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: 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-450/+bug/1918582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918582] Re: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1918582 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: I changed to use the nvidia-driver-460(proprietary,tested) and this error keep popping up everytime i logged in ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 (not installed) ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-44-generic Date: Tue Mar 9 23:41:30 2021 DuplicateSignature: dkms:nvidia-kernel-source-450:450.51.05-0ubuntu1:/var/lib/dkms/nvidia/450.51.05/build/common/inc/nv-linux.h:508:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2021-02-22 (16 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 450.51.05-0ubuntu1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: 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-450/+bug/1918582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918583] [NEW] Switch to libgpiod and disable CONFIG_GPIO_SYSFS
Public bug reported: Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153 debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y However, this interface got deprecated for removal: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134 "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020." https://www.kernel.org/doc/Documentation/gpio/sysfs.txt "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED." libgpiod and the use of a character file-based interface is a replacement to the sysfs interface: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used: sudo gpioget gpiochip0 12 gpioget: error reading GPIO values: Device or resource busy sudo gpioinfo | grep 12 line 12: "GPIO12" "sysfs" input active-high [used] It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_GPIO_SYSFS=n" ** 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/1918583 Title: Switch to libgpiod and disable CONFIG_GPIO_SYSFS Status in linux package in Ubuntu: New Bug description: Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153 debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y However, this interface got deprecated for removal: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134 "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020." https://www.kernel.org/doc/Documentation/gpio/sysfs.txt "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED." libgpiod and the use of a character file-based interface is a replacement to the sysfs interface: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used: sudo gpioget gpiochip0 12 gpioget: error reading GPIO values: Device or resource busy sudo gpioinfo | grep 12 line 12: "GPIO12" "sysfs" input active-high [used] It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_GPIO_SYSFS=n" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918586] [NEW] File system becomes read only during upgrade
Public bug reported: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "terminal.txt" https://bugs.launchpad.net/bugs/1918586/+attachment/5475612/+files/terminal.txt -- 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/1918586 Title: File system becomes read only during upgrade Status in linux-firmware package in Ubuntu: New Bug description: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918586] Re: File system becomes read only during upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1918586 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1918586 Title: File system becomes read only during upgrade Status in linux-firmware package in Ubuntu: Incomplete Bug description: I was alerted this morning by monitoring that a file system had become read-only. Upon inspection of the server I could see it had just finished updated (attempted to) automatically. I attempted to resolve the issue and the host went down. I then started my hot spare which is exactly the same hardware (Intel NUC) and same OS version 20.04 and as it been off for months applied the updates. During the upgrade of linux-firmware the system locked up and then eventually threw the error you can see in the terminal transcript attached. The system is then in a state where it is unable to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1918586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918583] 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 1918583 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/1918583 Title: Switch to libgpiod and disable CONFIG_GPIO_SYSFS Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153 debian.master/config/config.common.ubuntu: CONFIG_GPIO_SYSFS=y However, this interface got deprecated for removal: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0910d72afc69b25703f7be9bf7d13f18937a478 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe95046e960b4b76e73dc1486955d93f47276134 "This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020." https://www.kernel.org/doc/Documentation/gpio/sysfs.txt "THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED." libgpiod and the use of a character file-based interface is a replacement to the sysfs interface: https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/ Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used: sudo gpioget gpiochip0 12 gpioget: error reading GPIO values: Device or resource busy sudo gpioinfo | grep 12 line 12: "GPIO12" "sysfs" input active-high [used] It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_GPIO_SYSFS=n" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916467] Re: [Intel Maple Ridge] system cannot enter S3 the first time while connecting to TBT4 storage
** Tags added: originate-from-1912438
--
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/1916467
Title:
[Intel Maple Ridge] system cannot enter S3 the first time while
connecting to TBT4 storage
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
Systems with Intel Maple Ridge addon card with tbt devices attached may
fail to suspend/resume.
[Fix]
Commit 319696aa80 ("xhci: Fix repeated xhci wake after suspend due to
uncleared internal wake state") currently landed in
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git branch
for-usb-linus.
[Test Case]
When booted from unpatched kernel, starting from oem-5.10 that has
received Intel Maple Ridge enablement fixes, XHCI port on Maple Ridge
card may wake itself unsolicitedly when performing runtime/deep suspend:
kernel: [326] pci_pme_active:2422: xhci_hcd :37:00.0: PME# disabled
kernel: [326] __pci_set_master:4219: xhci_hcd :37:00.0: enabling bus
mastering
kernel: [326] pci_save_state:1553: xhci_hcd :37:00.0: saving config
space at offset 0x0 (reading 0x11388086)
...
kernel: [326] pci_pme_active:2422: xhci_hcd :37:00.0: PME# enabled
The suspend resume process will stuck forever.
[Where problems could occur]
Tried on a few more platforms, didn't found possible regression.
== original bug description ==
[Reproduce Steps]
1. install TBT4 card
2. Boot into Ubuntu X68
3. suspend and wake up to confirm S3 function
3. Connect TBT storage
4. suspend
5. system cannot enter S3
[Results]
Expected Result: system enters suspend
Actual Result: 1st attempt fails, screen will be turned off but power & fan
won't. system can only enter s3 afterwards
Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=211377
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1916467/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909647] Re: xfrm_policy.sh in net from ubuntu_kernel_selftests passed with failed sub-cases
** Description changed:
[Impact]
Even with failed cases reported in the xfrm_policy.sh test, the overall
result is still "PASS"
$ sudo ./xfrm_policy.sh
# selftests: net: xfrm_policy.sh
# PASS: policy before exception matches
# FAIL: expected ping to .254 to fail (exceptions)
# PASS: direct policy matches (exceptions)
# PASS: policy matches (exceptions)
# FAIL: expected ping to .254 to fail (exceptions and block policies)
# PASS: direct policy matches (exceptions and block policies)
# PASS: policy matches (exceptions and block policies)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
hresh changes)
# PASS: direct policy matches (exceptions and block policies after hresh
changes)
# PASS: policy matches (exceptions and block policies after hresh changes)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
hthresh change in ns3)
# PASS: direct policy matches (exceptions and block policies after hthresh
change in ns3)
# PASS: policy matches (exceptions and block policies after hthresh change
in ns3)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
htresh change to normal)
# PASS: direct policy matches (exceptions and block policies after htresh
change to normal)
# PASS: policy matches (exceptions and block policies after htresh change to
normal)
# PASS: policies with repeated htresh change
ok 12 selftests: net: xfrm_policy.sh
$ echo $?
0
This is because of the variable "lret" in check_xfrm() is not a local
variable, and it looks like it will override the one in
check_exceptions() thus making the return value become 0 for the passed
test case after the failed one.
[Fix]
* f6e9ceb7a7fc32 (" selftests: xfrm: fix test return value override issue in
xfrm_policy.sh")
+ Focal kernel got this patch via stable update, and we don't have this
+ test in Bionic. Only Groovy and OEM-5.6 are affected.
+
This patch can be cherry-picked into all of the affected kernels.
- Focal kernel got this patch via stable update, and we don't have this
- test in Bionic.
-
[Test]
- Run the xfrm_policy.sh test, if there is any failed cases the final result
will not be 0.
+ Run the xfrm_policy.sh test, if there is any failed case the final result
will not be 0.
[Regression Potential]
This change is just for testing tools, it's unlikely to affect real kernel
functionality. However it's expected to generate failures in our test report as
it's reflecting the real test result.
** Tags added: groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1909647
Title:
xfrm_policy.sh in net from ubuntu_kernel_selftests passed with failed
sub-cases
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[Impact]
Even with failed cases reported in the xfrm_policy.sh test, the overall
result is still "PASS"
$ sudo ./xfrm_policy.sh
# selftests: net: xfrm_policy.sh
# PASS: policy before exception matches
# FAIL: expected ping to .254 to fail (exceptions)
# PASS: direct policy matches (exceptions)
# PASS: policy matches (exceptions)
# FAIL: expected ping to .254 to fail (exceptions and block policies)
# PASS: direct policy matches (exceptions and block policies)
# PASS: policy matches (exceptions and block policies)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
hresh changes)
# PASS: direct policy matches (exceptions and block policies after hresh
changes)
# PASS: policy matches (exceptions and block policies after hresh changes)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
hthresh change in ns3)
# PASS: direct policy matches (exceptions and block policies after hthresh
change in ns3)
# PASS: policy matches (exceptions and block policies after hthresh change
in ns3)
# FAIL: expected ping to .254 to fail (exceptions and block policies after
htresh change to normal)
# PASS: direct policy matches (exceptions and block policies after htresh
change to normal)
# PASS: policy matches (exceptions and block policies after htresh change to
normal)
# PASS: policies with repeated htresh change
ok 12 selftests: net: xfrm_policy.sh
$ echo $?
0
This is because
