[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P
verified linux-firmware/focal-proposed version 1.187.19 has identical blobs with those tested and proposed. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946304] Re: amdgpu: Add initial firmware for navi24 Beige Goby
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux-firmware-
staging starting from 1.187.19+staging.28
--
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/1946304
Title:
amdgpu: Add initial firmware for navi24 Beige Goby
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Won't Fix
Status in linux-firmware source package in Focal:
In Progress
Bug description:
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
- linux-firmware is being under reviewed in
https://lore.kernel.org/linux-
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946304] Re: amdgpu: Add initial firmware for navi24 Beige Goby
The kernel driver targets oem-5.14 and Impish has 5.13, so only Focal is
nominated for now.
** Changed in: linux-firmware (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/1946304
Title:
amdgpu: Add initial firmware for navi24 Beige Goby
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Won't Fix
Status in linux-firmware source package in Focal:
In Progress
Bug description:
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
- linux-firmware is being under reviewed in
https://lore.kernel.org/linux-
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946304] [NEW] amdgpu: Add initial firmware for navi24 Beige Goby
Public bug reported:
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
- linux-firmware is being under reviewed in
https://lore.kernel.org/linux-
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: Won't Fix
** Affects: linux-firmware (Ubuntu Focal)
Importance: High
Assignee: You-Sheng Yang (vicamo)
Status: In Progress
** Tags: hwe-graphics oem-priority originate-from-1928296 somerville
** Tags added: oem-priority originate-from-1928296 somerville
** Also affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1946304
Title:
amdgpu: Add initial firmware for navi24 Beige Goby
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Won't Fix
Status in linux-firmware source package in Focal:
In Progress
Bug description:
- This GPU is needed for AMD R21M-P50-50
- amdgpu upstream driver already landed kernel v5.14.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
[git.kernel.org]
/* BEIGE_GOBY */
{0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
{0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
- linux-firmware is being under reviewed in
https://lore.kernel.org/linux-
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946304/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946303] [NEW] No video after wake from S3 due to Nvidia driver crash
Public bug reported: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "crashes seen via journalctl" https://bugs.launchpad.net/bugs/1946303/+attachment/5531172/+files/nvidia_resume_crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946128] Re: ubuntu_lxc: Fails multiple tests
Hello Tim, thanks for the report, these are actually failing with something like: Downloading the image index ERROR: Invalid signature for /tmp/tmp.u1JHG6CYmL/index.asc And the api_test.py is failing with this issue as well. I will modify the bug title / description for this. ** Summary changed: - ubuntu_lxc: Fails multiple tests + ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid signature" ** Tags added: 5.11 aws focal sru-20210927 ubuntu-lxc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946128 Title: ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid signature" Status in ubuntu-kernel-tests: New Status in linux-aws-5.11 package in Ubuntu: New Bug description: linux-aws-5.11 5.11.0-1020.21~20.04.2 ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small All failures are identical: CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=1, Command returned non-zero exit status CmdError: Command failed, rc=2, Command returned non-zero exit status I do not see the same failures when run manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] System freeze
You can either: * Stay on Nvidia-460; or * Wait and just test each new update of Nvidia-470.xx as it is released; or * Report the problem to Nvidia directly. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => New ** Summary changed: - [nvidia] System freeze + [nvidia] System freeze using nvidia-470 but nvidia-460 is fine -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: [nvidia] System freeze using nvidia-470 but nvidia-460 is fine Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Today's 3rd crash report. Is there anything useful in these logs? ** Attachment added: "prevboot-2021-10-06-c.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531156/+files/prevboot-2021-10-06-c.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1946288] [NEW] iGVT-g guest freezes if idle for too long
Public bug reported: A Windows 10 iGVT-g guest is crashing if left idle for too long. "Too long" can mean hours or even minutes with no load. The QEMU command line is: /usr/bin/qemu-system-x86_64 -name Windows 10 -nodefaults -M pc,usb=true -machine kernel_irqchip=on -enable-kvm -mem-prealloc -mem-path /dev/hugepages/qemu -device qemu-xhci,id=qemu-xhci,addr=4,p2=15,p3=15,streams=on,command_serr_enable=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -drive file=./images/redm.qcow2,if=virtio -cpu host -smp sockets=1,cores=2,threads=1 -m 8192M -bios /usr/share/seabios/bios.bin -device usb-tablet,id=tablet,bus=qemu-xhci.0,port=1 -vga none -monitor vc -serial stdio -display gtk,gl=on -device vfio-pci-nohotplug,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4-448a-9f09-7b93adbf672c,x-igd-opregion=on,display=on,addr=0x3,rombar=0,id=iHD520,ramfb=on -device ivshmem-plain,memdev=HMB -object memory-backend-file,id=HMB,size=4M,mem-path=/dev/shm/test,share=on -netdev user,id=net0,hostfwd=::33890-:3389,smb=./TOSHIBA2TB/ -device virtio-net-pci,netdev=net0,id=n0,addr=0x8 -monitor telnet:127.0.0.1:5,server,nowait Normally, I use the machine pc-i440fx-3.1 but I set the latest one (pc, or pc-i440fx-4.2) for testing, which didn't fix this freeze. In this state, it's not possible to reclaim the memory and the virtual GPU, they are stuck until the computer is powered off. After this QEMU guest freeze, it is impossible to power off the computer cleanly: it's required to forcefully shutdown, as the system fails to The telnet server from the guest still connect, but doesn't respond. I installed the OEM kernel to get the 5.14 version of the kernel. Testing with drm-tip (commit 7c36ed237585ed2f645439e62dafccac070d5e33, from August), I was able to left the guest idle for hours with no problem multiple times, but using Ubuntu's generic (5.4, 5.8, 5.11) or oem (5.14) kernel this freeze is happening. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1004-oem 5.14.0-1004.4 ProcVersionSignature: Ubuntu 5.14.0-1004.4-oem 5.14.5 Uname: Linux 5.14.0-1004-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Oct 6 21:33:41 2021 InstallationDate: Installed on 2017-06-13 (1576 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2019-12-22 (654 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946288 Title: iGVT-g guest freezes if idle for too long Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: A Windows 10 iGVT-g guest is crashing if left idle for too long. "Too long" can mean hours or even minutes with no load. The QEMU command line is: /usr/bin/qemu-system-x86_64 -name Windows 10 -nodefaults -M pc,usb=true -machine kernel_irqchip=on -enable-kvm -mem-prealloc -mem-path /dev/hugepages/qemu -device qemu-xhci,id=qemu-xhci,addr=4,p2=15,p3=15,streams=on,command_serr_enable=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -drive file=./images/redm.qcow2,if=virtio -cpu host -smp sockets=1,cores=2,threads=1 -m 8192M -bios /usr/share/seabios/bios.bin -device usb-tablet,id=tablet,bus=qemu-xhci.0,port=1 -vga none -monitor vc -serial stdio -display gtk,gl=on -device vfio-pci-nohotplug,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4-448a-9f09-7b93adbf672c,x-igd-opregion=on,display=on,addr=0x3,rombar=0,id=iHD520,ramfb=on -device ivshmem-plain,memdev=HMB -object memory-backend-file,id=HMB,size=4M,mem-path=/dev/shm/test,share=on -netdev user,id=net0,hostfwd=::33890-:3389,smb=./TOSHIBA2TB/ -device virtio-net-pci,netdev=net0,id=n0,addr=0x8 -monitor telnet:127.0.0.1:5,server,nowait Normally, I use the machine pc-i440fx-3.1 but I set the latest one (pc, or pc-i440fx-4.2) for testing, which didn't fix this freeze. In this state, it's not possible to reclaim the memory and the virtual GPU, they are stuck until the computer is powered off. After this QEMU guest freeze, it is impossible to power off the computer cleanly: it's required to forcefully shutdown, as the system fails to The telnet server from the guest still connect, but doesn't respond. I installed the OEM kernel to get the 5.14 version of the kernel. Testing with drm-tip (commit 7c36ed237585ed2f645439e62dafccac070d5e33, from August), I was able to left the guest idle for hours with no problem multiple times, but using Ubuntu's generic (5.4, 5.8, 5.11) or oem (5.14) kernel this freeze is happening. ProblemType: Bug
Re: [Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hello, I’d just like to report that I haven’t seen this problem in a while. The last time I see the “retry page fault” messages in my log was on August 9. I’ve been using the ‘amdgpu/picasso*‘ files from linux-firmware commit c46b8c364b82 (“ice: update package file to 1.3.26.0”) so apparently this particular problem was recently fixed. Which isn’t to say that I’m having a trouble-free amdgpu experience, unfortunately. Every week or so my laptop comes back from sleep with the screen and keyboard frozen (I can still ssh into it), but now the error is: kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out But it seems to be a separate problem from the one reported in this particular launchpad issue. I’ll see if I can find a more appropriate launchpad issue and post the details there. Thank you all for your help and support with this issue. -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945376] Re: [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the laptop
Hi mate, thanks for getting back to me, I have checked the dmesg after touchpad freezing, but I couldn't see anything related to i2c. Any idea? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945376 Title: [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the laptop Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on my Asus ZenBook flip always stops working after I close the laptop! I have to restart the computer to make working again. Appreciate your support. Thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Sep 29 08:55:00 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Iris Xe Graphics [1043:1362] InstallationDate: Installed on 2021-03-14 (198 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX363EA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX363EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: ZenBook UX363EA_UX371EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
For the record, 4.15.0-1113-aws works in r5.metal w/ kexec. Booted it 10 times successfully from both 5.4.0-1058-aws and 4.15.0-1113-aws (itself.) (not that it was expected to make a difference as the issue happens on normal boot, which doesn't have previous kernel.) Right after that, in the same instance, trying a normal boot fails. And it had kdump installed/enabled (ie, crashkernel in cmdline), w/ which Ian mentioned that he couldn't reproduce the problem. --- It also works on normal boot w/ r5d.metal (note 'd'), which should be the same as r5.metal but w/ four local nvme disks. (still boots from EBS/nvme disk in the same way as r5.metal) --- Similarly, it works on r4.24xlarge (this is not metal) but does boot from EBS/nvme disk too. --- So it seems like there's no problem with the patchset as in 4.15.0-1113-aws as it boots fine in several types w/ approx the same hardware config, just differing on normal/kexec in the r5.metal type (problem report.) - r5.metal: normal boot fails / kexec boot works - r5d.metal: normal boot works. - r5.24xlarge: normal boot works. The kexec boot worked ~20 times, so it wouldn't seem like a race condition is in place, as that should be enough runs, considering it failed every time on normal boot. Also, Ian mentioned that he couldn't reproduce w/ crashdump installed. Well, I think the only difference it would cause _before_ mounting the rootfs (assuming that's what doesn't work/allow machine to boot, as we have no serial console) is the crashkernel reservation? --- So, all this is a bit confusing, but seem to indicate again that there's no problem w/ the patchset per se, but perhaps something in booting this particular kernel on a particular instance type (r5.metal) which _might_ be related to normal/ kexec/crashkernel boot differences. More tomorrow. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946219] Re: liburing stops working after upgrading to 5.4.0-1012
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946219 Title: liburing stops working after upgrading to 5.4.0-1012 Status in HWE Next: New Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946266] [NEW] Add psample tunnel support and also two fixes for psample issues.
Public bug reported: * Explain the bug(s) Fix psample compilation issue and add tunnel support * brief explanation of fixes Enhance psample * How to test Add tc rule with tunnel and sample actions and run traffic. Verify sample traffic on the sample interface. * What it could break. psample could be broke as new function is enabled ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946266 Title: Add psample tunnel support and also two fixes for psample issues. Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) Fix psample compilation issue and add tunnel support * brief explanation of fixes Enhance psample * How to test Add tc rule with tunnel and sample actions and run traffic. Verify sample traffic on the sample interface. * What it could break. psample could be broke as new function is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945369] Re: memory cgroup disabled on Ubuntu Core 18
Discovered how do to it, had to add 'cgroup_enable=memory cgroup_memory=1' to '/ubuntu-seed/cmdline' of the sd card. -- 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/1945369 Title: memory cgroup disabled on Ubuntu Core 18 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs to be manually enabled. I was able to enable it by adding `cgroup_enable=memory cgroup_memory=1` to the kernel command line, but on Ubuntu I think the memory cgroup should be enabled by default shouldn't it? $ cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset2 1 1 cpu 4 100 1 cpuacct 4 100 1 blkio 5 100 1 memory0 109 0 devices 6 100 1 freezer 9 4 1 net_cls 3 1 1 perf_event10 1 1 net_prio 3 1 1 pids 8 107 1 rdma 7 1 1 I see this with Linux localhost 5.4.0-1043-raspi #47~18.04.1-Ubuntu SMP PREEMPT Mon Aug 23 14:39:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux on Ubuntu Core 18, but folks have informed me that the same is true on Ubuntu Core 20 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Today's 2nd crash report. Is there anything useful in these logs? ** Attachment added: "prevboot-2021-10-06-b.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531117/+files/prevboot-2021-10-06-b.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1942215]
Created attachment 1158 broken dsdt from notebook -- 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/1942215 Title: OOPs on boot: invalid opcode: [#1] SMP NOPTI Status in Linux: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: Incomplete Bug description: Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon boot on vought we get this: ... [ 11.502916] invalid opcode: [#1] SMP NOPTI [ 11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 5.13.0-15-generic #15-Ubuntu [ 11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774 [ 11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01 [ 11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286 [ 11.513428] RAX: RBX: 8f08a7573800 RCX: 0040 [ 11.514972] RDX: RSI: 91ea9980 RDI: 02cb [ 11.516100] RBP: aaeca1a77710 R08: R09: 8f08a8c84af0 [ 11.517479] R10: R11: 0003 R12: [ 11.518985] R13: 8f08a8c84af0 R14: R15: [ 11.520425] FS: 7f7fb403ed00() GS:8f348d5c() knlGS: [ 11.521931] CS: 0010 DS: ES: CR0: 80050033 [ 11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 007706e0 [ 11.524924] DR0: DR1: DR2: [ 11.526221] DR3: DR6: fffe0ff0 DR7: 0400 [ 11.527636] PKRU: 5554 [ 11.528820] Call Trace: [ 11.529807] acpi_ps_parse_loop+0x587/0x660 [ 11.531198] acpi_ps_parse_aml+0x1af/0x552 [ 11.532595] acpi_ps_execute_method+0x208/0x2ca [ 11.533972] acpi_ns_evaluate+0x34e/0x4f0 [ 11.535361] acpi_evaluate_object+0x18e/0x3b4 [ 11.536736] acpi_evaluate_dsm+0xb3/0x120 [ 11.537943] ? acpi_evaluate_dsm+0xb3/0x120 [ 11.539214] nfit_intel_shutdown_status+0xed/0x1b0 [nfit] [ 11.540603] acpi_nfit_add_dimm+0x3cb/0x670 [nfit] [ 11.541990] acpi_nfit_register_dimms+0x141/0x460 [nfit] [ 11.543377] acpi_nfit_init+0x54f/0x620 [nfit] [ 11.544755] acpi_nfit_add+0x192/0x1f0 [nfit] [ 11.546116] acpi_device_probe+0x49/0x170 [ 11.547431] really_probe+0x245/0x4c0 [ 11.548749] driver_probe_device+0xf0/0x160 [ 11.550064] device_driver_attach+0xab/0xb0 [ 11.551387] __driver_attach+0xb2/0x140 [ 11.552692] ? device_driver_attach+0xb0/0xb0 [ 11.554001] bus_for_each_dev+0x7e/0xc0 [ 11.555326] driver_attach+0x1e/0x20 [ 11.556630] bus_add_driver+0x135/0x1f0 [ 11.557917] driver_register+0x95/0xf0 [ 11.559226] acpi_bus_register_driver+0x39/0x50 [ 11.560139] nfit_init+0x168/0x1000 [nfit] [ 11.561230] ? 0xc0649000 [ 11.562442] do_one_initcall+0x46/0x1d0 [ 11.563701] ? kmem_cache_alloc_trace+0x11c/0x240 [ 11.564846] do_init_module+0x62/0x290 [ 11.565768] load_module+0xaa6/0xb40 [ 11.566811] __do_sys_finit_module+0xc2/0x120 [ 11.567825] __x64_sys_finit_module+0x18/0x20 [ 11.568747] do_syscall_64+0x61/0xb0 [ 11.569694] ? syscall_exit_to_user_mode+0x27/0x50 [ 11.570680] ? __x64_sys_mmap+0x33/0x40 [ 11.571606] ? do_syscall_64+0x6e/0xb0 [ 11.572442] ? asm_exc_page_fault+0x8/0x30 [ 11.573395] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 11.574392] RIP: 0033:0x7f7fb45d670d [ 11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48 [ 11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 0139 [ 11.578573] RAX: ffda RBX: 5624b212e410 RCX: 7f7fb45d670d [ 11.579646] RDX: RSI: 7f7fb47683fe RDI: 0006 [ 11.580712] RBP: 0002 R08: R09: [ 11.581774] R10: 0006 R11: 0246 R12: 7f7fb47683fe [ 11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 5624b2096cd0 [ 11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel msr ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear ast drm_vram_helper i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul drm_kms_helper
[Kernel-packages] [Bug 1946229] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1946229/+attachment/5531114/+files/CRDA.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946229 Title: ZTE Modem USB stick not recognized Status in linux package in Ubuntu: Confirmed Bug description: ~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead device' error. [qua out 6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using xhci_hcd [qua out 6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1588, bcdDevice= 0.00 [qua out 6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=5 [qua out 6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device detected [qua out 6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0 [qua out 6 09:47:21 2021] usb 1-3: USB disconnect, device number 19 [qua out 6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using xhci_hcd [qua out 6 09:47:22 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1589, bcdDevice= 0.00 [qua out 6 09:47:22 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=13 [qua out 6 09:47:22 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:22 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:22 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:22 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-3, ZTE CDC Ethernet Device, 06:df:4b:52:02:fd [qua out 6 09:47:22 2021] option 1-3:1.2: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 [qua out 6 09:47:22 2021] option 1-3:1.3: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1 [qua out 6 09:47:22 2021] option 1-3:1.4: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2 [qua out 6 09:47:22 2021] option 1-3:1.5: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB3 [qua out 6 09:47:22 2021] usb-storage 1-3:1.6: USB Mass Storage device detected [qua out 6 09:47:22 2021] scsi host4: usb-storage 1-3:1.6 [qua out 6 09:47:23 2021] scsi 4:0:0:0: CD-ROMZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] scsi 4:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0 [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi generic sg4 type 5 [qua out 6 09:47:59 2021] sd 4:0:0:1: Attached scsi generic sg5 type 0 [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B) [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write Enabled [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Asking for cache data failed [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through [qua out 6 09:48:04 2021] usb 1-3: USB disconnect, device number 20 [qua out 6 09:48:04 2021] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device [qua out 6 09:48:04 2021] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [qua out 6 09:48:04 2021] option 1-3:1.2: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [qua out 6 09:48:04 2021] option 1-3:1.3: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [qua out 6 09:48:04 2021] option 1-3:1.4: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [qua out 6 09:48:04 2021] option 1-3:1.5: device disconnected [qua out 6 09:48:04 2021] sd 4:0:0:1: [sdd] Attached SCSI removable disk [qua out 6 09:48:04 2021] scsi 4:0:0:0: rejecting I/O to dead device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3
[Kernel-packages] [Bug 1946229] Re: ZTE Modem USB stick not recognized
apport information ** Tags added: apport-collected ** Description changed: ~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead device' error. [qua out 6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using xhci_hcd [qua out 6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1588, bcdDevice= 0.00 [qua out 6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=5 [qua out 6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device detected [qua out 6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0 [qua out 6 09:47:21 2021] usb 1-3: USB disconnect, device number 19 [qua out 6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using xhci_hcd [qua out 6 09:47:22 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1589, bcdDevice= 0.00 [qua out 6 09:47:22 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=13 [qua out 6 09:47:22 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:22 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:22 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:22 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-3, ZTE CDC Ethernet Device, 06:df:4b:52:02:fd [qua out 6 09:47:22 2021] option 1-3:1.2: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 [qua out 6 09:47:22 2021] option 1-3:1.3: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1 [qua out 6 09:47:22 2021] option 1-3:1.4: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2 [qua out 6 09:47:22 2021] option 1-3:1.5: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB3 [qua out 6 09:47:22 2021] usb-storage 1-3:1.6: USB Mass Storage device detected [qua out 6 09:47:22 2021] scsi host4: usb-storage 1-3:1.6 [qua out 6 09:47:23 2021] scsi 4:0:0:0: CD-ROMZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] scsi 4:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0 [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi generic sg4 type 5 [qua out 6 09:47:59 2021] sd 4:0:0:1: Attached scsi generic sg5 type 0 [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B) [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write Enabled [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Asking for cache data failed [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through [qua out 6 09:48:04 2021] usb 1-3: USB disconnect, device number 20 [qua out 6 09:48:04 2021] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device [qua out 6 09:48:04 2021] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [qua out 6 09:48:04 2021] option 1-3:1.2: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [qua out 6 09:48:04 2021] option 1-3:1.3: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [qua out 6 09:48:04 2021] option 1-3:1.4: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [qua out 6 09:48:04 2021] option 1-3:1.5: device disconnected [qua out 6 09:48:04 2021] sd 4:0:0:1: [sdd] Attached SCSI removable disk [qua out 6 09:48:04 2021] scsi 4:0:0:0: rejecting I/O to dead device + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: josue 2566 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-09-30 (6 days ago) + InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + MachineType: Dell Inc. Inspiron 7560 +
[Kernel-packages] [Bug 1946245] Re: Impish update: v5.13.16 upstream stable release
** Changed in: linux (Ubuntu Impish) 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/1946245 Title: Impish update: v5.13.16 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: 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: v5.13.16 upstream stable release from git://git.kernel.org/ firmware: dmi: Move product_sku info to the end of the modalias igmp: Add ip_mc_list lock in ip_check_mc_rcu net: ll_temac: Remove left-over debug message Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM" blk-mq: fix kernel panic during iterating over flush request blk-mq: fix is_flush_rq blk-mq: clearing flush request reference in tags->rqs[] ALSA: usb-audio: Add registration quirk for JBL Quantum 800 Bluetooth: Add additional Bluetooth part for Realtek 8852AE Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic usb: host: xhci-rcar: Don't reload firmware after the completion usb: xhci-mtk: fix issue of out-of-bounds array access usb: cdnsp: fix the wrong mult value for HS isoc or intr usb: gadget: tegra-xudc: fix the wrong mult value for HS isoc or intr usb: mtu3: restore HS function when set SS/SSP usb: mtu3: use @mult for HS isoc or intr usb: mtu3: fix the wrong HS mult value xhci: fix even more unsafe memory usage in xhci tracing xhci: fix unsafe memory usage in xhci tracing xhci: Fix failure to give back some cached cancelled URBs. x86/reboot: Limit Dell Optiplex 990 quirk to early BIOS versions PCI: Call Max Payload Size-related fixup quirks early Linux 5.13.16 UBUNTU: upstream stable to v5.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946242] Re: Impish update: v5.13.15 upstream stable release
** Changed in: linux (Ubuntu Impish) 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/1946242 Title: Impish update: v5.13.15 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: 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: v5.13.15 upstream stable release from git://git.kernel.org/ ext4: fix e2fsprogs checksum failure for mounted filesystem gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats reset: reset-zynqmp: Fixed the argument data type qed: Fix the VF msix vectors flow net: dsa: mv88e6xxx: Update mv88e6393x serdes errata riscv: dts: microchip: Use 'local-mac-address' for emac1 riscv: dts: microchip: Add ethernet0 to the aliases node net: macb: Add a NULL check on desc_ptp qede: Fix memset corruption perf/x86/intel/pt: Fix mask of num_address_ranges ceph: fix possible null-pointer dereference in ceph_mdsmap_decode() perf/x86/amd/ibs: Work around erratum #1197 perf/x86/amd/power: Assign pmu.module cryptoloop: add a deprecation warning xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG USB: serial: pl2303: fix GL type detection USB: serial: cp210x: fix control-characters error handling USB: serial: cp210x: fix flow-control error handling ALSA: hda/realtek: Quirk for HP Spectre x360 14 amp setup ALSA: usb-audio: Fix regression on Sony WALKMAN NW-A45 DAC ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17 ALSA: pcm: fix divide error in snd_pcm_lib_ioctl media: stkwebcam: fix memory leak in stk_camera_probe Linux 5.13.15 UBUNTU: upstream stable to v5.13.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946247] Re: Impish update: v5.13.17 upstream stable release
** Changed in: linux (Ubuntu Impish) 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/1946247 Title: Impish update: v5.13.17 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: 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: v5.13.17 upstream stable release from git://git.kernel.org/ locking/mutex: Fix HANDOFF condition regmap: fix the offset of register error log regulator: tps65910: Silence deferred probe error crypto: mxs-dcp - Check for DMA mapping errors sched/deadline: Fix reset_on_fork reporting of DL tasks power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() sched/deadline: Fix missing clock update in migrate_task_rq_dl() rcu/tree: Handle VM stoppage in stall detection EDAC/mce_amd: Do not load edac_mce_amd module on guests hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() hrtimer: Ensure timerfd notification for HIGHRES=n udf: Check LVID earlier udf: Fix iocharset=utf8 mount option isofs: joliet: Fix iocharset=utf8 mount option bcache: add proper error unwinding in bcache_device_init nbd: add the check to prevent overflow in __nbd_ioctl() blk-throtl: optimize IOPS throttle for large IO scenarios nvme-tcp: don't update queue count when failing to set io queues nvme-rdma: don't update queue count when failing to set io queues nvmet: pass back cntlid on successful completion power: supply: smb347-charger: Add missing pin control activation power: supply: max17042_battery: fix typo in MAx17042_TOFF s390/cio: add dev_busid sysfs entry for each subchannel s390/zcrypt: fix wrong offset index for APKA master key valid state libata: fix ata_host_start() sched/topology: Skip updating masks for non-online nodes crypto: omap - Fix inconsistent locking of device lists crypto: qat - do not ignore errors from enable_vf2pf_comms() crypto: qat - handle both source of interrupt in VF ISR crypto: qat - fix reuse of completion variable crypto: qat - fix naming for init/shutdown VF to PF notifications crypto: qat - do not export adf_iov_putmsg() crypto: hisilicon/sec - fix the abnormal exiting process crypto: hisilicon/sec - modify the hardware endian configuration crypto: tcrypt - Fix missing return value check fcntl: fix potential deadlocks for _struct.lock fcntl: fix potential deadlock for _struct.fa_lock udf_get_extendedattr() had no boundary checks. io-wq: remove GFP_ATOMIC allocation off schedule out path s390/kasan: fix large PMD pages address alignment check s390/pci: fix misleading rc in clp_set_pci_fn() s390/debug: keep debug data on resize s390/debug: fix debug area life cycle s390/ap: fix state machine hang after failure to enable irq sched/debug: Don't update sched_domain debug directories before sched_debug_init() power: supply: cw2015: use dev_err_probe to allow deferred probe m68k: emu: Fix invalid free in nfeth_cleanup() crypto: x86/aes-ni - add missing error checks in XTS code crypto: ecc - handle unaligned input buffer in ecc_swap_digits sched/numa: Fix is_core_idle() sched: Fix UCLAMP_FLAG_IDLE setting rcu: Fix to include first blocked task in stall warning rcu: Fix stall-warning deadlock due to non-release of rcu_node ->lock m68k: Fix invalid RMW_INSNS on CPUs that lack CAS block: return ELEVATOR_DISCARD_MERGE if possible spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config spi: spi-pic32: Fix issue with uninitialized dma_slave_config genirq/timings: Fix error return code in irq_timings_test_irqs() irqchip/loongson-pch-pic: Improve edge triggered interrupt support lib/mpi: use kcalloc in mpi_resize clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel block: nbd: add sanity check for first_minor spi: coldfire-qspi: Use clk_disable_unprepare in the remove function irqchip/apple-aic: Fix irq_disable from within irq handlers irqchip/gic-v3: Fix priority comparison when non-secure priorities are used crypto: qat - use proper type for vf_mask certs: Trigger creation of RSA module signing key if it's not an RSA key tpm: ibmvtpm: Avoid error message when process gets signal while waiting io_uring: refactor
[Kernel-packages] [Bug 1946249] Re: Impish update: v5.13.18 upstream stable release
** Changed in: linux (Ubuntu Impish) 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/1946249 Title: Impish update: v5.13.18 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: 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: v5.13.18 upstream stable release from git://git.kernel.org/ Note: v5.13.18 contained only reverts for commits omitted from our application of v5.13.17, so v5.13.18 applied to Impish is just the "Linux 5.13.18" release commit. Linux 5.13.18 UBUNTU: upstream stable to v5.13.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946229] 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 1946229 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 ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946229 Title: ZTE Modem USB stick not recognized Status in linux package in Ubuntu: Incomplete Bug description: ~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead device' error. [qua out 6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using xhci_hcd [qua out 6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1588, bcdDevice= 0.00 [qua out 6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=5 [qua out 6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device detected [qua out 6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0 [qua out 6 09:47:21 2021] usb 1-3: USB disconnect, device number 19 [qua out 6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using xhci_hcd [qua out 6 09:47:22 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1589, bcdDevice= 0.00 [qua out 6 09:47:22 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=13 [qua out 6 09:47:22 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:22 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:22 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:22 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-3, ZTE CDC Ethernet Device, 06:df:4b:52:02:fd [qua out 6 09:47:22 2021] option 1-3:1.2: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 [qua out 6 09:47:22 2021] option 1-3:1.3: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1 [qua out 6 09:47:22 2021] option 1-3:1.4: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2 [qua out 6 09:47:22 2021] option 1-3:1.5: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB3 [qua out 6 09:47:22 2021] usb-storage 1-3:1.6: USB Mass Storage device detected [qua out 6 09:47:22 2021] scsi host4: usb-storage 1-3:1.6 [qua out 6 09:47:23 2021] scsi 4:0:0:0: CD-ROMZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] scsi 4:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0 [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi generic sg4 type 5 [qua out 6 09:47:59 2021] sd 4:0:0:1: Attached scsi generic sg5 type 0 [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B) [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write Enabled [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Asking for cache data failed [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through [qua out 6 09:48:04 2021] usb 1-3: USB disconnect, device number 20 [qua out 6 09:48:04 2021] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device [qua out 6 09:48:04 2021] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [qua out 6 09:48:04 2021] option 1-3:1.2: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [qua out 6 09:48:04 2021] option 1-3:1.3: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [qua out 6 09:48:04 2021]
[Kernel-packages] [Bug 1946229] Re: ZTE Modem USB stick not recognized
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946229 Title: ZTE Modem USB stick not recognized Status in linux package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead device' error. [qua out 6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using xhci_hcd [qua out 6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1588, bcdDevice= 0.00 [qua out 6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=5 [qua out 6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device detected [qua out 6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0 [qua out 6 09:47:21 2021] usb 1-3: USB disconnect, device number 19 [qua out 6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using xhci_hcd [qua out 6 09:47:22 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1589, bcdDevice= 0.00 [qua out 6 09:47:22 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=13 [qua out 6 09:47:22 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:22 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:22 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:22 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-3, ZTE CDC Ethernet Device, 06:df:4b:52:02:fd [qua out 6 09:47:22 2021] option 1-3:1.2: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 [qua out 6 09:47:22 2021] option 1-3:1.3: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1 [qua out 6 09:47:22 2021] option 1-3:1.4: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2 [qua out 6 09:47:22 2021] option 1-3:1.5: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB3 [qua out 6 09:47:22 2021] usb-storage 1-3:1.6: USB Mass Storage device detected [qua out 6 09:47:22 2021] scsi host4: usb-storage 1-3:1.6 [qua out 6 09:47:23 2021] scsi 4:0:0:0: CD-ROMZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] scsi 4:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0 [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi generic sg4 type 5 [qua out 6 09:47:59 2021] sd 4:0:0:1: Attached scsi generic sg5 type 0 [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B) [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write Enabled [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Asking for cache data failed [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through [qua out 6 09:48:04 2021] usb 1-3: USB disconnect, device number 20 [qua out 6 09:48:04 2021] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device [qua out 6 09:48:04 2021] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [qua out 6 09:48:04 2021] option 1-3:1.2: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [qua out 6 09:48:04 2021] option 1-3:1.3: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [qua out 6 09:48:04 2021] option 1-3:1.4: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [qua out 6 09:48:04 2021] option 1-3:1.5: device disconnected [qua out 6 09:48:04 2021] sd 4:0:0:1: [sdd] Attached SCSI removable disk [qua out 6 09:48:04 2021] scsi 4:0:0:0: rejecting I/O to dead device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1946229] [NEW] ZTE Modem USB stick not recognized
You have been subscribed to a public bug: ~$ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to dead device' error. [qua out 6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using xhci_hcd [qua out 6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1588, bcdDevice= 0.00 [qua out 6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=5 [qua out 6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device detected [qua out 6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0 [qua out 6 09:47:21 2021] usb 1-3: USB disconnect, device number 19 [qua out 6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using xhci_hcd [qua out 6 09:47:22 2021] usb 1-3: New USB device found, idVendor=19d2, idProduct=1589, bcdDevice= 0.00 [qua out 6 09:47:22 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=13 [qua out 6 09:47:22 2021] usb 1-3: Product: ZTE Mobile Broadband Station [qua out 6 09:47:22 2021] usb 1-3: Manufacturer: ZTE,Incorporated [qua out 6 09:47:22 2021] usb 1-3: SerialNumber: 1234567890ABCDEF [qua out 6 09:47:22 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at usb-:00:14.0-3, ZTE CDC Ethernet Device, 06:df:4b:52:02:fd [qua out 6 09:47:22 2021] option 1-3:1.2: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0 [qua out 6 09:47:22 2021] option 1-3:1.3: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1 [qua out 6 09:47:22 2021] option 1-3:1.4: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2 [qua out 6 09:47:22 2021] option 1-3:1.5: GSM modem (1-port) converter detected [qua out 6 09:47:22 2021] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB3 [qua out 6 09:47:22 2021] usb-storage 1-3:1.6: USB Mass Storage device detected [qua out 6 09:47:22 2021] scsi host4: usb-storage 1-3:1.6 [qua out 6 09:47:23 2021] scsi 4:0:0:0: CD-ROMZTE USB SCSI CD-ROM 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] scsi 4:0:0:1: Direct-Access ZTE MMC Storage 2.31 PQ: 0 ANSI: 0 CCS [qua out 6 09:47:23 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0 [qua out 6 09:47:59 2021] sr 4:0:0:0: Attached scsi generic sg4 type 5 [qua out 6 09:47:59 2021] sd 4:0:0:1: Attached scsi generic sg5 type 0 [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 B) [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write Enabled [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Asking for cache data failed [qua out 6 09:47:59 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through [qua out 6 09:48:04 2021] usb 1-3: USB disconnect, device number 20 [qua out 6 09:48:04 2021] cdc_ether 1-3:1.0 usb0: unregister 'cdc_ether' usb-:00:14.0-3, ZTE CDC Ethernet Device [qua out 6 09:48:04 2021] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [qua out 6 09:48:04 2021] option 1-3:1.2: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [qua out 6 09:48:04 2021] option 1-3:1.3: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [qua out 6 09:48:04 2021] option 1-3:1.4: device disconnected [qua out 6 09:48:04 2021] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [qua out 6 09:48:04 2021] option 1-3:1.5: device disconnected [qua out 6 09:48:04 2021] sd 4:0:0:1: [sdd] Attached SCSI removable disk [qua out 6 09:48:04 2021] scsi 4:0:0:0: rejecting I/O to dead device ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ZTE Modem USB stick not recognized https://bugs.launchpad.net/bugs/1946229 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 1942181] Re: Add support for AlderLake CPUs
This bug was fixed in the package thermald - 2.4.3-1ubuntu3 --- thermald (2.4.3-1ubuntu3) hirsute; urgency=medium * AlderLake CPU support (LP: #1942181) - 0015-Add-AlderLake-cpu-model.patch - 0016-Update-sysfs-paths-for-Alader-Lake.patch -- Colin King Mon, 31 Aug 2021 09:36:12 +0100 ** Changed in: thermald (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Released Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946249] [NEW] Impish update: v5.13.18 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.18 upstream stable release from git://git.kernel.org/ Note: v5.13.18 contained only reverts for commits omitted from our application of v5.13.17, so v5.13.18 applied to Impish is just the "Linux 5.13.18" release commit. Linux 5.13.18 UBUNTU: upstream stable to v5.13.18 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Impish) 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 Impish) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** 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: + v5.13.18 upstream stable release -v5.13.18 upstream stable release -from git://git.kernel.org/ + Note: v5.13.18 contained only reverts for commits omitted from our + application of v5.13.17, so the v5.13.18 applied to Impish is just + the "Linux 5.13.18" release commit. + + from git://git.kernel.org/ + + Linux 5.13.18 + UBUNTU: upstream stable to v5.13.18 ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.18 upstream stable release - Note: v5.13.18 contained only reverts for commits omitted from our - application of v5.13.17, so the v5.13.18 applied to Impish is just - the "Linux 5.13.18" release commit. + Note: v5.13.18 contained only reverts for commits omitted from our + application of v5.13.17, so v5.13.18 applied to Impish is just + the "Linux 5.13.18" release commit. from git://git.kernel.org/ Linux 5.13.18 UBUNTU: upstream stable to v5.13.18 ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.18 upstream stable release + from git://git.kernel.org/ Note: v5.13.18 contained only reverts for commits omitted from our application of v5.13.17, so v5.13.18 applied to Impish is just the "Linux 5.13.18" release commit. - from git://git.kernel.org/ - Linux 5.13.18 UBUNTU: upstream stable to v5.13.18 -- 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/1946249 Title: Impish update: v5.13.18 upstream stable release Status in linux package in Ubuntu:
[Kernel-packages] [Bug 1946247] Re: Impish update: v5.13.17 upstream stable release
** 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: + v5.13.17 upstream stable release + from git://git.kernel.org/ -v5.13.17 upstream stable release -from git://git.kernel.org/ + locking/mutex: Fix HANDOFF condition + regmap: fix the offset of register error log + regulator: tps65910: Silence deferred probe error + crypto: mxs-dcp - Check for DMA mapping errors + sched/deadline: Fix reset_on_fork reporting of DL tasks + power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors + crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() + sched/deadline: Fix missing clock update in migrate_task_rq_dl() + rcu/tree: Handle VM stoppage in stall detection + EDAC/mce_amd: Do not load edac_mce_amd module on guests + hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() + hrtimer: Ensure timerfd notification for HIGHRES=n + udf: Check LVID earlier + udf: Fix iocharset=utf8 mount option + isofs: joliet: Fix iocharset=utf8 mount option + bcache: add proper error unwinding in bcache_device_init + nbd: add the check to prevent overflow in __nbd_ioctl() + blk-throtl: optimize IOPS throttle for large IO scenarios + nvme-tcp: don't update queue count when failing to set io queues + nvme-rdma: don't update queue count when failing to set io queues + nvmet: pass back cntlid on successful completion + power: supply: smb347-charger: Add missing pin control activation + power: supply: max17042_battery: fix typo in MAx17042_TOFF + s390/cio: add dev_busid sysfs entry for each subchannel + s390/zcrypt: fix wrong offset index for APKA master key valid state + libata: fix ata_host_start() + sched/topology: Skip updating masks for non-online nodes + crypto: omap - Fix inconsistent locking of device lists + crypto: qat - do not ignore errors from enable_vf2pf_comms() + crypto: qat - handle both source of interrupt in VF ISR + crypto: qat - fix reuse of completion variable + crypto: qat - fix naming for init/shutdown VF to PF notifications + crypto: qat - do not export adf_iov_putmsg() + crypto: hisilicon/sec - fix the abnormal exiting process + crypto: hisilicon/sec - modify the hardware endian configuration + crypto: tcrypt - Fix missing return value check + fcntl: fix potential deadlocks for _struct.lock + fcntl: fix potential deadlock for _struct.fa_lock + udf_get_extendedattr() had no boundary checks. + io-wq: remove GFP_ATOMIC allocation off schedule out path + s390/kasan: fix large PMD pages address alignment check + s390/pci: fix misleading rc in clp_set_pci_fn() + s390/debug: keep debug data on resize + s390/debug: fix debug area life cycle + s390/ap: fix state machine hang after failure to enable irq + sched/debug: Don't update sched_domain debug directories before sched_debug_init() + power: supply: cw2015: use dev_err_probe to allow deferred probe + m68k: emu: Fix invalid free in nfeth_cleanup() + crypto: x86/aes-ni - add missing error checks in XTS code + crypto: ecc - handle unaligned input buffer in ecc_swap_digits + sched/numa: Fix is_core_idle() + sched: Fix UCLAMP_FLAG_IDLE setting + rcu: Fix to include first blocked task in stall warning + rcu: Fix stall-warning deadlock due to non-release of rcu_node ->lock + m68k: Fix invalid RMW_INSNS on CPUs that lack CAS + block: return ELEVATOR_DISCARD_MERGE if possible + spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config + spi: spi-pic32: Fix issue with uninitialized dma_slave_config + genirq/timings: Fix error return code in irq_timings_test_irqs() + irqchip/loongson-pch-pic: Improve edge triggered interrupt support + lib/mpi: use kcalloc in mpi_resize + clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel + block: nbd: add sanity check for first_minor + spi: coldfire-qspi: Use clk_disable_unprepare in the remove function + irqchip/apple-aic: Fix irq_disable from within irq handlers + irqchip/gic-v3: Fix priority comparison when non-secure priorities are used + crypto: qat - use proper type for vf_mask + certs: Trigger creation of RSA module
[Kernel-packages] [Bug 1946247] [NEW] Impish update: v5.13.17 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.17 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Impish) 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 Impish) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1946247 Title: Impish update: v5.13.17 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: 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: v5.13.17 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946245] [NEW] Impish update: v5.13.16 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.16 upstream stable release from git://git.kernel.org/ firmware: dmi: Move product_sku info to the end of the modalias igmp: Add ip_mc_list lock in ip_check_mc_rcu net: ll_temac: Remove left-over debug message Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM" blk-mq: fix kernel panic during iterating over flush request blk-mq: fix is_flush_rq blk-mq: clearing flush request reference in tags->rqs[] ALSA: usb-audio: Add registration quirk for JBL Quantum 800 Bluetooth: Add additional Bluetooth part for Realtek 8852AE Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic usb: host: xhci-rcar: Don't reload firmware after the completion usb: xhci-mtk: fix issue of out-of-bounds array access usb: cdnsp: fix the wrong mult value for HS isoc or intr usb: gadget: tegra-xudc: fix the wrong mult value for HS isoc or intr usb: mtu3: restore HS function when set SS/SSP usb: mtu3: use @mult for HS isoc or intr usb: mtu3: fix the wrong HS mult value xhci: fix even more unsafe memory usage in xhci tracing xhci: fix unsafe memory usage in xhci tracing xhci: Fix failure to give back some cached cancelled URBs. x86/reboot: Limit Dell Optiplex 990 quirk to early BIOS versions PCI: Call Max Payload Size-related fixup quirks early Linux 5.13.16 UBUNTU: upstream stable to v5.13.16 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Impish) 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 Impish) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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: + v5.13.16 upstream stable release + from git://git.kernel.org/ -v5.13.16 upstream stable release -from git://git.kernel.org/ + firmware: dmi: Move product_sku info to the end of the modalias + igmp: Add ip_mc_list lock in ip_check_mc_rcu + net: ll_temac: Remove left-over debug message + Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM" + blk-mq: fix kernel panic during iterating over flush request + blk-mq: fix is_flush_rq + blk-mq: clearing flush request reference in tags->rqs[] + ALSA: usb-audio: Add registration quirk for JBL Quantum 800 + Bluetooth: Add additional Bluetooth part for Realtek 8852AE + Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic + usb: host: xhci-rcar: Don't reload firmware after the completion + usb: xhci-mtk: fix issue of out-of-bounds array access + usb: cdnsp: fix the wrong mult value for HS isoc or intr + usb: gadget: tegra-xudc: fix the wrong mult value for HS isoc or intr + usb: mtu3: restore HS function when set SS/SSP + usb: mtu3: use @mult for HS isoc or intr + usb: mtu3: fix the wrong HS mult value + xhci: fix even more unsafe memory usage in xhci tracing + xhci: fix unsafe memory usage in xhci tracing + xhci: Fix failure to give back some cached cancelled URBs. + x86/reboot: Limit Dell Optiplex 990 quirk to early BIOS versions + PCI: Call Max Payload Size-related fixup quirks early + Linux 5.13.16 + UBUNTU: upstream stable to
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
BTW, do you know of the differences between r5.metal and r5.24xlarge? Per the specs they seem to be the same as in cpu/ram/nic/_nvme_ storage, but differ in baremetal vs nitro hypervisor? The reason I ask is because downgrading from 5.4.0-1056-aws to 4.15.0-1113-aws worked/booted fine on r5.24xlarge, differently from r5.metal. I got to test it while looking for a similar instance type that had serial console support, but it didn't repro the problem, actually. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946242] [NEW] Impish update: v5.13.15 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.15 upstream stable release from git://git.kernel.org/ ext4: fix e2fsprogs checksum failure for mounted filesystem gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats reset: reset-zynqmp: Fixed the argument data type qed: Fix the VF msix vectors flow net: dsa: mv88e6xxx: Update mv88e6393x serdes errata riscv: dts: microchip: Use 'local-mac-address' for emac1 riscv: dts: microchip: Add ethernet0 to the aliases node net: macb: Add a NULL check on desc_ptp qede: Fix memset corruption perf/x86/intel/pt: Fix mask of num_address_ranges ceph: fix possible null-pointer dereference in ceph_mdsmap_decode() perf/x86/amd/ibs: Work around erratum #1197 perf/x86/amd/power: Assign pmu.module cryptoloop: add a deprecation warning xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG USB: serial: pl2303: fix GL type detection USB: serial: cp210x: fix control-characters error handling USB: serial: cp210x: fix flow-control error handling ALSA: hda/realtek: Quirk for HP Spectre x360 14 amp setup ALSA: usb-audio: Fix regression on Sony WALKMAN NW-A45 DAC ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17 ALSA: pcm: fix divide error in snd_pcm_lib_ioctl media: stkwebcam: fix memory leak in stk_camera_probe Linux 5.13.15 UBUNTU: upstream stable to v5.13.15 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Impish) 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 Impish) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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: + v5.13.15 upstream stable release + from git://git.kernel.org/ -v5.13.15 upstream stable release -from git://git.kernel.org/ + ext4: fix e2fsprogs checksum failure for mounted filesystem + gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats + reset: reset-zynqmp: Fixed the argument data type + qed: Fix the VF msix vectors flow + net: dsa: mv88e6xxx: Update mv88e6393x serdes errata + riscv: dts: microchip: Use 'local-mac-address' for emac1 + riscv: dts: microchip: Add ethernet0 to the aliases node + net: macb: Add a NULL check on desc_ptp + qede: Fix memset corruption + perf/x86/intel/pt: Fix mask of num_address_ranges + ceph: fix possible null-pointer dereference in ceph_mdsmap_decode() + perf/x86/amd/ibs: Work around erratum #1197 + perf/x86/amd/power: Assign pmu.module + cryptoloop: add a deprecation warning + xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG + USB: serial: pl2303: fix GL type detection + USB: serial: cp210x: fix control-characters error handling + USB: serial: cp210x: fix flow-control error handling + ALSA: hda/realtek: Quirk for HP Spectre x360 14 amp setup + ALSA: usb-audio: Fix regression on Sony WALKMAN NW-A45 DAC + ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17 + ALSA: pcm: fix divide error in snd_pcm_lib_ioctl + media: stkwebcam: fix memory leak in stk_camera_probe + Linux 5.13.15 + UBUNTU: upstream stable to v5.13.15 -- You received this
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
It looks like it's not a problem with the patchset in general, maybe it's specific to aws 4.15? The patchset is in 5.4.0-1058-aws and it booted fine here too. I'll check the patchset in 4.15.0-1113-aws. A difference from your comment is that I could _not_ boot it after 5.4.0-1058-aws, which worked for you. (r5.metal usually boots in ~15min? and it's been ~20min already and no response; serial console/screenshot is not availabe on bare metal sadly.) -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945749] Re: [nvidia] System freeze
It's been 3 days since I switch to nvidia drivers 460 and there have been no freeze or crash so far. I really hope that it is not a coincidence since most freeze/crash seemed to happen randomly. If this is indeed a problem with the specific version of the nvidia driver, is there anything I can do to fix this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945749 Title: [nvidia] System freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: System randomly freezes, no clue how to reproduce it. Multiple people have the same issue. Dell Precision 5550 running Ubuntu 20.04.3 LTS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 1 10:41:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-36-generic, x86_64: installed nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:097e] Subsystem: Dell TU117GLM [Quadro T1000 Mobile] [1028:097e] InstallationDate: Installed on 2021-08-27 (34 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=42e96b11-9efb-45e0-ace2-85fe35b2047b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0V6K79 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd08/11/2021:br1.9:svnDellInc.:pnPrecision5550:pvr:sku097E:rvnDellInc.:rn0V6K79:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5550 dmi.product.sku: 097E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944417] Re: Add support for 5.14
Tested against 5.14 and 5.11.0-38 on amd64 against the ubuntu ZFS regression tests, all pass OK. Marking this as verified. ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944417 Title: Add support for 5.14 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Invalid Status in zfs-linux source package in Hirsute: Fix Committed Bug description: == SRU Hirsute == [Impact] Add support for 5.14 kernels in Hirsute for zfs-linux dkms module. zfs-linux needs compat changes in order to build against 5.14 kernel like oem-5.14 in focal: - Linux-5.12-compat-bio-bi_disk-member-moved.patch - Linux-5.12-compat-replace-bio_-_io_acct-with-disk_-_.patch - Linux-5.12-compat-idmapped-mounts.patch - Linux-5.12-update-bio_max_segs-replaces-BIO_MAX_PAGE.patch - Remove-iov_iter_advance-for-iter_write.patch - linux-5.13-compat-bdevops-revalidate_disk-removed.patch - Linux-5.14-compat-blk_alloc_disk.patch - Linux-5.14-compat-explicity-assign-set_page_dirty.patch - Linux-5.14-compat-META.patch [Test Plan] Run the ubuntu ZFS regressions tests, these cover smoke testing core functionality, POSIX fs semantics, subset of xfs tests and all mount options with file system stress-ng stress tests. see git://kernel.ubuntu.com/ubuntu/autotest-client/tests/ubuntu_zfs* tests [Where problems could occur] in BIO and block allocation layers in ZFS. These are exercised extensively by the ZFS regression tests. The 5.12..5.14 compat options are dkms build time config checks, so build testing the zfs-dkms package with 5.11 and 5.14 kernels will ensure these dkms build-time options are exercised. [Other Info] These Linux 5.12..5.14 compat patches are in Ubuntu impish and have had some testing already, so the regression potential is low as these code paths have already had some exposure to real work loads. Tested on x86-64 with 5.11 and 5.14 kernels to exercise the build-time dkms config kernel detection paths. Exercised with the ubuntu zfs regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945553] Re: It hangs while booting up with AMD W6800 [1002:73A3]
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1015.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945553 Title: It hangs while booting up with AMD W6800 [1002:73A3] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] It hangs when booting up with AMD W6800 [1002:73A3] graphics card. [Fix] Bisect the kernel and found below fix from v5.15-rc1 mainline kernel 5810323ba692 drm/amd/pm: Fix a bug communicating with the SMU (v5) [Test] Verified the patch on a Dell workstation with AMD W6800 graphics card [Where problems could occur] The code flow doesn't change much, but with better return codes handling and print out more meaningful messages. So it should not impact the already working devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** Description changed: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal - flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 - kernel installation, but still wouldn't boot after installing the 4.15 - kernel. + flush. Removed 'discard' from mount options and rebooted 5.4 kernel + prior to 4.15 kernel installation, but still wouldn't boot after + installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Today's first report. Is there anything useful in these logs? ** Attachment added: "prevboot-2021-10-06-a.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5531096/+files/prevboot-2021-10-06-a.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Confirmed it does work to first upgrade bionic/linux-5.4 from 5.4.0-1056-aws to 5.4.0-1058-aws and then update to 4.15.0-1113-aws -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946231] [NEW] esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)
Public bug reported: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x >> firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description:Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 14:59:58 2021 InstallationDate: Installed on 2020-08-29 (403 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946231 Title: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341) Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package:
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Hey Ian, thanks for the bug report! I'm checking this on AWS. -- 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/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943923] Re: Fix i915 warnings on skl_dram_get_channel_info()
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1943923 Title: Fix i915 warnings on skl_dram_get_channel_info() Status in HWE Next: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: [Impact] Kernel warning from i915's skl_dram_get_channel_info(). [Fix] Update how i915 gets DRAM information. [Test] No more kernel splat after the fix gets applied. Anything graphics related seems to work fine. [Where problems could occur] The change only applies to gen11 and gen12 gfx so the scope is limited. If the PCODE doesn't work as intended, this might cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945932 Title: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system 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-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 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 Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] *** this issue happen with secure boot on and issue gone when secure boot is off*** After the BIOS loading screen, a yellow screen pops up in an instant (< 1 second) and then disappears. Attached a demo video. [Fix] do what intel_color_commit() does to make sure the bottom color state matches whatever out hardware readout produced. Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1 [Test] 1. Power on the system 2. Check if any unusual screen shows before and after the system loading screen. 3. No unusual screen shows before and after the system loading screen [Regression Potential] Medium, maintainer still not totally sure what should do about color management features here in general. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-azure source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> 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 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 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: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-azure source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> 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 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 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: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Found on 2021.09.27/bionic/linux-azure-fips/4.15.0-2037.41 only instance Standard_D48_v3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-azure source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> 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 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 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: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-azure source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> 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 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 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: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-azure source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> 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 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 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: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 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/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] Re: With Nvidia-470 there is no option to use Wayland on the login screen
Alberto, what's the rational to have ubuntu-drivers doing the kms configuration there? Wouldn't it be more robust to have it in the deb or generated in the postinst? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With Nvidia-470 there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946032] Re: NFS client fails to mount with timeout on kernel 5.4.0-1057-aws
The crux of the issue seems to be the use of privileged ports, which are (and should be) blocked by network ACL in our environment: The functional server instance is using a non-privileged port 56242: tcp 0 0 10.99.19.46:56242 10.99.16.151:2049 ESTABLISHED The non-functional server is trying to use a privileged port 978: 116 27.617188 10.99.19.43 10.99.16.151TCP 76 978 → 2049 [SYN] Seq=0 Win=62727 Len=0 MSS=8961 SACK_PERM=1 TSval=906311050 TSecr=0 WS=128 As a result, the non-working server is unable to establish a connection with EFS to mount. This behaviour happens with this kernel version (https://launchpad.net/ubuntu/+source/linux-aws/5.4.0-1057.60 only so far): It appears that this kernel ignores the "noresvport" mount option. ** Tags added: kernel-bug ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1946032 Title: NFS client fails to mount with timeout on kernel 5.4.0-1057-aws Status in linux-aws-5.4 package in Ubuntu: New Bug description: On an Ubuntu 18.04.1 server, I mount AWS EFS filesystems with nfsv4.1 successfully on ec2 instances. Mounts work on kernel version 5.4.0-1056-aws but if i upgrade the kernel to 5.4.0-1057-aws the mounts stop working with a network timeout, due to port 111 being blocked as its not needed for nfsv4 Issue started to happen when apt daily automatically upgraded the kernel version. I reproduced by rolling back kernel version on the same instance and doing mounts successfully, then reverting to newer kernel (plus reboot) and getting the network timeout issue. Mount command is identical in all cases and follows AWS Documentation ``` sudo mount -t nfs -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport mount-target-DNS:/ ~/efs-mount-point ``` Could it be a kernel bug or misconfiguration, what can i do ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1946032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946222] [NEW] presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' in the 'linux-firmware' package causes Intel AX210 wifi to cease functioning
Public bug reported: When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' exists (after a fresh OS installation & after updates to the 'linux-firmware' package)--wifi fails to function: $ lspci -knn | grep Net -A3 93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:4020] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep iwlwifi [2.390962] iwlwifi :93:00.0: enabling device ( -> 0002) [2.412571] iwlwifi :93:00.0: api flags index 2 larger than supported by driver [2.412585] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [2.412827] iwlwifi :93:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [2.433308] iwlwifi :93:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [2.582482] iwlwifi :93:00.0: loaded PNVM version 0x324cd670 [2.830634] iwlwifi :93:00.0: Timeout waiting for PNVM load! [2.830639] iwlwifi :93:00.0: Failed to start RT ucode: -110 [2.830643] iwlwifi :93:00.0: iwl_trans_send_cmd bad state = 1 [3.034634] iwlwifi :93:00.0: firmware didn't ACK the reset - continue anyway [3.046824] iwlwifi :93:00.0: Failed to run INIT ucode: -110 When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' is deleted, or renamed-- wifi works: $ lspci -knn | grep Net -A3 93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:4020] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep iwlwifi [3.425668] iwlwifi :93:00.0: enabling device ( -> 0002) [3.436377] iwlwifi :93:00.0: api flags index 2 larger than supported by driver [3.436392] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [3.436634] iwlwifi :93:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [3.459053] iwlwifi :93:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [3.698849] iwlwifi :93:00.0: base HW address: a0:e7:0b:5a:ec:77 [3.716331] iwlwifi :93:00.0 wlp147s0: renamed from wlan0 --1-- $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 --2-- $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.17 Candidate: 1.187.17 Version table: *** 1.187.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages --3-- Expectation: Intel AX210 wifi works without having to perform extra steps to rename/delete files after linux-firmware package updates --4-- Reality: Intel AX210 wifi does not work without performing extra steps to rename/delete files after linux-firmware package updates I have no idea where the .pnvm file is coming from as it is not present in the files provided by Intel at https://www.intel.com/content/www/us/en/support/articles/05511/wireless.html Please consider removing the .pnvm files from all versions of the 'linux-firmware' package... currently found in these versions: 1 pnvm file - https://packages.ubuntu.com/focal-updates/all/linux- firmware/filelist 2 pnvm files - https://packages.ubuntu.com/impish/all/linux- firmware/filelist The pnvm file is not present in the Ubuntu 2104 (Hirsute) linux-firmware package and the AX210 wifi works perfectly well on that platform but it fails to function on 20.04 (Focal), where the pnvm is present, and will likely also fail in 21.10 (Impish). ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1946222 Title: presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' in the 'linux- firmware' package causes Intel AX210 wifi to cease functioning Status in linux-firmware package in Ubuntu: New Bug description: When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' exists (after a fresh OS installation & after updates to the 'linux-firmware' package)--wifi fails to function: $ lspci -knn | grep Net -A3 93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:4020] Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep iwlwifi [2.390962] iwlwifi :93:00.0: enabling device ( -> 0002) [2.412571] iwlwifi :93:00.0: api flags index 2 larger than supported by driver [2.412585] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [
[Kernel-packages] [Bug 1946108] Re: touchpad is not wokring at all, does not get recognized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946108 Title: touchpad is not wokring at all, does not get recognized Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Touchpad does not show after: cat /proc/bus/input/devices > ~/devices All drivers are up to date. Laptop is a: Fujitsu Lifebook U-7510 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 5 10:04:33 2021 InstallationDate: Installed on 2021-09-22 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946152] Re: my touchpad is not detected. I don't see it when I run 'xinput list' in the terminal.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946152 Title: my touchpad is not detected. I don't see it when I run 'xinput list' in the terminal. Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: Here is the output of the command line 'cat /proc/bus/input/devices' : I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=60070290 8380207af040d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="MSI WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=13 B: KEY=10003 30 e 0 B: MSC=10 I: Bus=0019 Vendor=0001 Product=0001 Version=0100 N: Name="gpio-keys" P: Phys=gpio-keys/input0 S: Sysfs=/devices/platform/ACPI0011:00/gpio-keys.1.auto/input/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=3 B: KEY=0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=5986 Product=211b Version=0302 N: Name="HD Webcam: HD Webcam" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input20 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=c077 Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C077.0004/input/input32 U: Uniq= H: Handlers=mouse0 event16 B: PROP=0 B: EV=17 B:
[Kernel-packages] [Bug 1946219] [NEW] liburing stops working after upgrading to 5.4.0-1012
Public bug reported: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: chelmsford oem-priority originate-from-1935996 ** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Tags added: chelmsford oem-priority originate-from-1935996 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946219 Title: liburing stops working after upgrading to 5.4.0-1012 Status in HWE Next: New Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: In Progress Bug description: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821905] Re: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4
Found on 2021.09.27/trusty/linux-azure/4.15.0-1125.138~14.04.1 -- 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/1821905 Title: umip in ubuntu_kvm_unit_test failed on T-3.13 / T-4.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This umip test failed on T-3.13 and T-4.4 On X-4.4 this was skipped: SKIP umip (qemu-system-x86_64: CPU feature umip not found) So it looks like a qemu issue to me. root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/umip.flat -smp 1 -cpu qemu64,+umip # -initrd /tmp/tmp.WBWyPcleSg CPU feature umip not found enabling apic UMIP=0, CPL=0 PASS: no exception from smsw PASS: no exception from sgdt PASS: no exception from sidt PASS: no exception from sldt PASS: no exception from str UMIP=0, CPL=3 PASS: no exception from smsw PASS: no exception from sgdt PASS: no exception from sidt PASS: no exception from sldt PASS: no exception from str PASS: exception from mov %cr0, %eax UMIP not available SUMMARY: 11 tests ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-143-generic 4.4.0-143.169~14.04.2 ProcVersionSignature: User Name 4.4.0-143.169~14.04.2-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Mar 27 11:10:13 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
Found on: 2021.09.27/trusty/linux-azure/4.15.0-1125.138~14.04.1 2021.09.27/bionic/linux-azure-fips/4.15.0-2037.41 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1940261 Title: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oracle package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux-oracle source package in Xenial: New Status in linux source package in Bionic: Incomplete Status in linux-oracle source package in Bionic: New Bug description: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: batch name: 11-basic-basic_errors test mode: c test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute
Found on: 2021.09.27/bionic/linux-azure-fips/4.15.0-2037.41 2021.09.27/bionic/linux-azure-4.15/4.15.0-1125.138 -- 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 timeout with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed 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 1946216] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1946216
Title:
PL2303GL chips not recognised by 21.10 beta
Status in linux package in Ubuntu:
Confirmed
Bug description:
L2303GL usb to serial chips are not recognised by the pl2303 module in
5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
chips are fairly common so it will cause a problem for users.
I reported this to the upstream maintainer and he confirmed it is a
known issue and fixed by commit dcf097e7d21f ("USB: serial: pl2303:
fix GL type detection"). Please backport for 21.10.
Email correspondence confirming bug pasted below.
Johan Hovold
9:33 AM (1 hour ago)
to me, linux-usb
On Tue, Oct 05, 2021 at 05:28:24PM +0100, Adrian Knagg-Baugh wrote:
> Hi,
> As requested in dmesg I'm reporting an unknown device type for the
> pl2303 driver. Here's the extract from dmesg:
>
> [ 2824.450073] usb 1-2: new full-speed USB device number 5 using xhci_hcd
> [ 2824.621910] usb 1-2: New USB device found, idVendor=067b,
> idProduct=23d3, bcdDevice= 4.05
> [ 2824.621922] usb 1-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
> [ 2824.621926] usb 1-2: Product: USB-Serial Controller
> [ 2824.621928] usb 1-2: Manufacturer: Prolific Technology Inc.
> [ 2824.621931] usb 1-2: SerialNumber: EKCRb19B616
> [ 2824.630068] pl2303 1-2:1.0: pl2303 converter detected
> [ 2824.630084] pl2303 1-2:1.0: unknown device type, please report to
> linux-...@vger.kernel.org
>
> adrian@mononoke:~$ uname -a
> Linux mononoke 5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC
> 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> The pl2303 is in a Skywatcher telescope synscan handset, the behaviour
> is a regression since it was working fine in the 5.11 kernels packaged
> with Ubuntu 21.04, it's only since updating to 5.13 (which I've had to
> do to resolve issues with the graphics card in my new laptop) that
> I've seen the problem.
>
> See below for the output of sudo lsusb -v
>
> I hope this helps.
Thanks for the report. This should already have been fixed by commit
dcf097e7d21f ("USB: serial: pl2303: fix GL type detection") which was
backported to v5.13.15 (released about a month ago).
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: adrian 1773 F pulseaudio
/dev/snd/controlC0: adrian 1773 F pulseaudio
/dev/snd/controlC1: adrian 1773 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 6 10:55:35 2021
InstallationDate: Installed on 2021-10-02 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G513IH_G513IH
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=8a2303d3-7aba-4e56-9501-3d719f7e2f1f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2021
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G513IH.310
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G513IH
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.68
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513IH.310:bd07/16/2021:br5.16:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGStrixG513IH_G513IH:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnG513IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G513IH_G513IH
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/1946216/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
It will be fixed in 22.04 at least: https://git.launchpad.net/~bluetooth/bluez/commit/?h=ubuntu- next=355b9c9e65f0c381aa606b9ce603f4ec70f8dc49 ** Changed in: bluez (Ubuntu) Status: Triaged => Fix Committed ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Fix Committed Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946216] [NEW] PL2303GL chips not recognised by 21.10 beta
Public bug reported:
L2303GL usb to serial chips are not recognised by the pl2303 module in
5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
chips are fairly common so it will cause a problem for users.
I reported this to the upstream maintainer and he confirmed it is a
known issue and fixed by commit dcf097e7d21f ("USB: serial: pl2303: fix
GL type detection"). Please backport for 21.10.
Email correspondence confirming bug pasted below.
Johan Hovold
9:33 AM (1 hour ago)
to me, linux-usb
On Tue, Oct 05, 2021 at 05:28:24PM +0100, Adrian Knagg-Baugh wrote:
> Hi,
> As requested in dmesg I'm reporting an unknown device type for the
> pl2303 driver. Here's the extract from dmesg:
>
> [ 2824.450073] usb 1-2: new full-speed USB device number 5 using xhci_hcd
> [ 2824.621910] usb 1-2: New USB device found, idVendor=067b,
> idProduct=23d3, bcdDevice= 4.05
> [ 2824.621922] usb 1-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 2824.621926] usb 1-2: Product: USB-Serial Controller
> [ 2824.621928] usb 1-2: Manufacturer: Prolific Technology Inc.
> [ 2824.621931] usb 1-2: SerialNumber: EKCRb19B616
> [ 2824.630068] pl2303 1-2:1.0: pl2303 converter detected
> [ 2824.630084] pl2303 1-2:1.0: unknown device type, please report to
> linux-...@vger.kernel.org
>
> adrian@mononoke:~$ uname -a
> Linux mononoke 5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC
> 2021 x86_64 x86_64 x86_64 GNU/Linux
>
> The pl2303 is in a Skywatcher telescope synscan handset, the behaviour
> is a regression since it was working fine in the 5.11 kernels packaged
> with Ubuntu 21.04, it's only since updating to 5.13 (which I've had to
> do to resolve issues with the graphics card in my new laptop) that
> I've seen the problem.
>
> See below for the output of sudo lsusb -v
>
> I hope this helps.
Thanks for the report. This should already have been fixed by commit
dcf097e7d21f ("USB: serial: pl2303: fix GL type detection") which was
backported to v5.13.15 (released about a month ago).
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: adrian 1773 F pulseaudio
/dev/snd/controlC0: adrian 1773 F pulseaudio
/dev/snd/controlC1: adrian 1773 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 6 10:55:35 2021
InstallationDate: Installed on 2021-10-02 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
MachineType: ASUSTeK COMPUTER INC. ROG Strix G513IH_G513IH
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=8a2303d3-7aba-4e56-9501-3d719f7e2f1f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2021
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: G513IH.310
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G513IH
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 0.68
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513IH.310:bd07/16/2021:br5.16:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGStrixG513IH_G513IH:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnG513IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G513IH_G513IH
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1946216
Title:
PL2303GL chips not recognised by 21.10 beta
Status in linux package in Ubuntu:
New
Bug description:
L2303GL usb to serial chips are not recognised by the pl2303 module in
5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux (the current 21.10 candidate kernel). These
chips are fairly common so it will cause a problem for users.
I reported this to the upstream maintainer and he confirmed it is a
known issue and fixed by commit dcf097e7d21f ("USB: serial: pl2303:
fix GL type detection").
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Won't Fix Status in linux-lts-xenial package in Ubuntu: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Won't Fix Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 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 nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
Is anyone still seeing a similar issue on current mainline? ** Tags added: sts -- 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/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] Re: With Nvidia-470 there is no option to use Wayland on the login screen
Also it's not a new installation. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With Nvidia-470 there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] Re: With Nvidia-470 there is no option to use Wayland on the login screen
I use: sudo apt install nvidia-driver-470 out of habit, and also because of bug 1946196. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With Nvidia-470 there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] Re: With Nvidia-470 there is no option to use Wayland on the login screen
Thanks Daniel, how did you enable the driver? That's probably bug #1943816 if that's a new installation, the issue is that ubuntu-drivers is the one writing the kms option since https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.2 but you only get that set if you enable the driver by using the right script ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With Nvidia-470 there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute
https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/commit/?id=40b4e82c5331e672c023ba15f779e5eee988d89a -- 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 timeout with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed 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 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
Is this bug still present in Ubuntu 21.10? If you find slightly different issues there then we should open new bugs for them. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) Status in gdm3 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: Lenovo ideapad 510-15IKB OS: Ubuntu 18.04 bionic Kernel: x86_64 Linux 4.15.0-20-generic DE: GNOME CPU: Intel Core i5-7200U @ 4x 3.1GHz GPU: Intel HD 620 + NVIDIA GeForce 940MX (Optimus) UEFI boot, Secure Boot disabled. I installed the proprietary graphics driver with Software Properties and Vulkan applications (e.g. vulkan-smoketest, Unreal Editor, SDK examples, Dolphin) were working fine. To get rid of tearing I added nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then ran update-grub && update-initramfs -u and rebooted. After doing that, Vulkan applications stopped working because they couldn't initialize the Vulkan swap chain until I reverted the changes to GRUB. Everything works as expected if lightdm is used instead of gdm3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute
Test from AWS: * 8 minutes to run on H-aws-5.11 a1.medium * 8 minutes to run on F-aws-5.4 t2.small * 8 minutes to run on F-aws-5.11 a1.medium * 8 minutes to run on F-aws-5.11 t2.small -- 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 timeout with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed 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 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
I can no longer reproduce this bug. I assume it got fixed at some point, either intentionally or as a side effect of some other upstream change. Marking it as invalid – I assume that's the right status for bugs that can no longer be reproduced? ** Changed in: linux (Ubuntu) Status: Triaged => 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/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini, and connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug). Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeatedly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data). - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand. - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now. The kernel panics lock up the entire system (forcing a hard power off). lt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly. The logs end some time before the panic occurs. /var/log/syslog: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4598145/+files/syslog The reset loops also occurred when I was using Ubuntu vivid. The kernel panics only happened after an upgrade to wily. Output of lsusb -v is attached. The issue was root caused to the device violating the Mass Storage protocol. Hence, the preferred way to resolve is the vendor provides updated firmware. WORKAROUND: echo 1bbb:f000:i | sudo tee /sys/module/usb_storage/parameters/quirks --- ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ais523 6233 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=bfbc4bf8-2e40-4799-bbef-9c5044c87007 InstallationDate: Installed on 2014-06-03 (648 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: wily Uname: Linux 4.2.0-32-generic x86_64 UpgradeStatus: Upgraded to wily on 2016-02-18 (22 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 12/04/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd12/04/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] [NEW] With Nvidia-470 there is no option to use Wayland on the login screen
Public bug reported: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: impish nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946200 Title: With Nvidia-470 there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Can someone please retest on Ubuntu 21.10? http://cdimage.ubuntu.com/daily-live/current/ ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-430 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute
Also on: 2021.09.27/bionic/linux-azure-4.15/4.15.0-1125.138 (Standard_B1ms, Standard_D48_v3) ** Tags added: hinted -- 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 timeout with Bionic/Focal/Hirsute Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux source package in Impish: Confirmed 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 1946185] Re: large-receive-offload no more tunable in 5.4.0-89-generic
Thanks Stefan, that at least explains why it changed! I think without knowing broken use-cases I'm ok with it then. Not what I'd expect to be ok under SRU terms but IIRC it was added in a similar way back then, so I'm not stopping you to remove/fix it under similar terms. I'm setting the state to "Won't Fix" to reflect that. It might happen that other users will spot other use cases that are more broken by it. In that case you might need to start a place to document common mitigations. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Won't Fix Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to:
[Kernel-packages] [Bug 1943539] Re: NVIDIA 470 kernel WARNING: CPU: 11 PID: 352896 at /var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm]
** Summary changed: - NVIDIA 470 kernel warning + NVIDIA 470 kernel WARNING: CPU: 11 PID: 352896 at /var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1943539 Title: NVIDIA 470 kernel WARNING: CPU: 11 PID: 352896 at /var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm] Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: I got the following error several times each day: 81424.410080] [ cut here ] [81424.410081] WARNING: CPU: 11 PID: 352896 at /var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574 nv_drm_master_set+0x27/0x30 [nvidia_drm] [81424.410084] Modules linked in: snd_usb_audio snd_usbmidi_lib cdc_ether usbnet r8152 mii ses enclosure scsi_transport_sas uas usb_storage thunderbolt xt_state xt_conntrack ipt_REJECT nf_reject_ipv4 nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp 8812au(OE) sctp ip6_udp_tunnel udp_tunnel ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep zram binfmt_misc nls_iso8859_1 btusb uvcvideo btrtl btbcm videobuf2_vmalloc videobuf2_memops btintel videobuf2_v4l2 videobuf2_common bluetooth videodev ecdh_generic mc ecc mei_hdcp joydev intel_rapl_msr snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp [81424.410115] snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi kvm_intel snd_hda_intel kvm snd_intel_dspcfg soundwire_intel iwlmvm soundwire_generic_allocation soundwire_cadence rapl snd_hda_codec mac80211 intel_cstate snd_hda_core libarc4 snd_hwdep soundwire_bus iwlwifi input_leds snd_soc_core thinkpad_acpi serio_raw processor_thermal_device processor_thermal_rfim ucsi_acpi nvram cfg80211 snd_compress elan_i2c ledtrig_audio efi_pstore ac97_bus wmi_bmof snd_pcm_dmaengine intel_wmi_thunderbolt snd_seq_midi typec_ucsi snd_seq_midi_event ee1004 8250_dw processor_thermal_mbox snd_pcm mei_me typec snd_rawmidi mei processor_thermal_rapl intel_rapl_common intel_pch_thermal intel_soc_dts_iosf snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid int3400_thermal acpi_thermal_rel acpi_pad nvidia_uvm(POE) sch_fq_codel coretemp msr [81424.410142] parport_pc ppdev lp parport binder_linux ashmem_linux(CE) sunrpc ip_tables x_tables autofs4 dm_crypt hid_logitech_hidpp wacom hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit aesni_intel drm_kms_helper syscopyarea crypto_simd sysfillrect sysimgblt fb_sys_fops cec cryptd glue_helper rc_core psmouse e1000e drm nvme intel_lpss_pci i2c_i801 intel_lpss i2c_smbus nvme_core idma64 xhci_pci rtsx_pci virt_dma xhci_pci_renesas wmi video pinctrl_cannonlake [81424.410163] CPU: 11 PID: 352896 Comm: gpu-manager Tainted: PWC OE 5.11.0-34-lowlatency #36~20.04.1-Ubuntu [81424.410164] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET59W (1.42 ) 04/27/2021 [81424.410165] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [81424.410167] Code: 0f 1f 00 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 05 ab 6c 00 00 48 89 e5 48 8b 40 28 e8 9f 40 be d1 84 c0 74 02 5d c3 <0f> 0b 5d c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 [81424.410168] RSP: 0018:9e5d84c63b20 EFLAGS: 00010246 [81424.410169] RAX: RBX: 8a9486ce4400 RCX: 0008 [81424.410170] RDX: c2b8fe98 RSI: 0296 RDI: c2b8fe60 [81424.410171] RBP: 9e5d84c63b20 R08: 0008 R09: 9e5d84c63b08 [81424.410171] R10: R11: c04151d8 R12: 8a925c9a9800 [81424.410172] R13: 8a933c608a80 R14: 0001 R15: 8a925c9a9800 [81424.410173] FS: 7f63e2203b80() GS:8a99bc4c() knlGS: [81424.410174] CS: 0010 DS: ES: CR0: 80050033 [81424.410175] CR2: 7f63e25e1c40 CR3: 0001139cc006 CR4: 003726e0 [81424.410176] DR0: DR1: DR2: [81424.410177] DR3: DR6: fffe0ff0 DR7: 0400 [81424.410178] Call Trace: [81424.410179]
[Kernel-packages] [Bug 1944955] Re: Update the 470 NVIDIA driver to 470.74
** Summary changed: - Update the 470 NVIDIA driver + Update the 470 NVIDIA driver to 470.74 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944955 Title: Update the 470 NVIDIA driver to 470.74 Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Bug description: Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.74 (470) == * New upstream release: - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Updated nvidia-bug-report.sh to search the systemd journal for gdm-x-session logs. - Fixed a bug that could prevent nvidia-xconfig from disabling the X Composite extension on version 1.20 of the X.org X server. - Fixed a build failure, "too many arguments to function 'get_user_pages'", when building the NVIDIA kernel module for Linux kernel v4.4.168. - Fixed a build failure, "implicit declaration of function do_gettimeofday", when building the NVIDIA kernel module for Linux kernel 5.0 release candidates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] Re: large-receive-offload no more tunable in 5.4.0-89-generic
Looking at the delta I found this change (referencing the upstream
commit which was received via upstream stable):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbcf24d153884439dad30484a0e3f02350692e4c
This sounds like LRO should not have been configurable and they
(upstram) fixed that now. And they claim any problem are not theirs...
(at least I read it that way).
Commit a02e8964eaf92 ("virtio-net: ethtool configurable LRO")
maps LRO to virtio guest offloading features and allows the
administrator to enable and disable those features via ethtool.
This leads to several issues:
- For a device that doesn't support control guest offloads, the "LRO"
can't be disabled triggering WARN in dev_disable_lro() when turning
off LRO or when enabling forwarding bridging etc.
- For a device that supports control guest offloads, the guest
offloads are disabled in cases of bridging, forwarding etc slowing
down the traffic.
Fix this by using NETIF_F_GRO_HW instead. Though the spec does not
guarantee packets to be re-segmented as the original ones,
we can add that to the spec, possibly with a flag for devices to
differentiate between GRO and LRO.
Further, we never advertised LRO historically before a02e8964eaf92
("virtio-net: ethtool configurable LRO") and so bridged/forwarded
configs effectively always relied on virtio receive offloads behaving
like GRO - thus even if this breaks any configs it is at least not
a regression.
Fixes: a02e8964eaf92 ("virtio-net: ethtool configurable LRO")
--
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/1946185
Title:
large-receive-offload no more tunable in 5.4.0-89-generic
Status in linux package in Ubuntu:
Won't Fix
Bug description:
While debugging a bug 1945868 I found something that I think is a separate
issue to that original report, hence this new bug.
I found the virtio-net behavior changing in an unexpected way in
5.4.0-89-generic that is currently in Focal-proposed.
1. 5.4.0-86-generic
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off
$ sudo ethtool --features enp1s0 lro on
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: on
$ sudo ethtool --features enp1s0 lro off
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off
2. 5.4.0-88-generic
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off
$ sudo ethtool --features enp1s0 lro on
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: on
$ sudo ethtool --features enp1s0 lro off
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off
3. 5.4.0-89-generic
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off [fixed]
$ sudo ethtool --features enp1s0 lro on
Cannot change large-receive-offload
Could not change any device features
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off [fixed]
$ sudo ethtool --features enp1s0 lro off
Cannot change large-receive-offload
$ sudo ethtool --show-features enp1s0 | grep large
large-receive-offload: off [fixed
I've installed/uninstalled the guest kernel twice but the above behavior
remained consistent and seemed to be only influenced by the new kernel.
The used guest config is the default that falls out of uvt-kvm, that means in
regard to this bug:
hvm
...
Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from
current Focal-updates.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 6 06:47 seq
crw-rw 1 root audio 116, 33 Oct 6 06:47 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
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/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic
root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0
[Kernel-packages] [Bug 1944417] Re: Add support for 5.14
current version in impish seems to build fine with 5.14 ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944417 Title: Add support for 5.14 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Invalid Status in zfs-linux source package in Hirsute: Fix Committed Bug description: == SRU Hirsute == [Impact] Add support for 5.14 kernels in Hirsute for zfs-linux dkms module. zfs-linux needs compat changes in order to build against 5.14 kernel like oem-5.14 in focal: - Linux-5.12-compat-bio-bi_disk-member-moved.patch - Linux-5.12-compat-replace-bio_-_io_acct-with-disk_-_.patch - Linux-5.12-compat-idmapped-mounts.patch - Linux-5.12-update-bio_max_segs-replaces-BIO_MAX_PAGE.patch - Remove-iov_iter_advance-for-iter_write.patch - linux-5.13-compat-bdevops-revalidate_disk-removed.patch - Linux-5.14-compat-blk_alloc_disk.patch - Linux-5.14-compat-explicity-assign-set_page_dirty.patch - Linux-5.14-compat-META.patch [Test Plan] Run the ubuntu ZFS regressions tests, these cover smoke testing core functionality, POSIX fs semantics, subset of xfs tests and all mount options with file system stress-ng stress tests. see git://kernel.ubuntu.com/ubuntu/autotest-client/tests/ubuntu_zfs* tests [Where problems could occur] in BIO and block allocation layers in ZFS. These are exercised extensively by the ZFS regression tests. The 5.12..5.14 compat options are dkms build time config checks, so build testing the zfs-dkms package with 5.11 and 5.14 kernels will ensure these dkms build-time options are exercised. [Other Info] These Linux 5.12..5.14 compat patches are in Ubuntu impish and have had some testing already, so the regression potential is low as these code paths have already had some exposure to real work loads. Tested on x86-64 with 5.11 and 5.14 kernels to exercise the build-time dkms config kernel detection paths. Exercised with the ubuntu zfs regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Kai-Heng, thank you for providing the test kernel. Folks, if you need to add pci=nocrs to your kernel-commandline to get your touchpad to work, please test this kernel: https://people.canonical.com/~khfeng/lp1878279/ With pci=no_e820 on the kernel commandline (replacing pci=nocrs). If the touchpad works this way, please provide DMI strings for your laptop, so that I can add a quirk to the kernel to automatically enable "pci=no_e820" on your laptop model. Run the following command *as normal user* to collect the DMI strings for your laptop: grep . /sys/class/dmi/id/* 2> /dev/null And copy and paste the output here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946183] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946183 Title: [Impish] No HDMI sound (AMD) Status in linux package in Ubuntu: Confirmed Bug description: Happens with official Impish 5.13 kernel or 5.15rc from unstable ckt ppa. Video is ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR 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 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530999/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] Re: large-receive-offload no more tunable in 5.4.0-89-generic
Tagged as regression-proposed because until we know better that is what it appears to me. Ran apport-collect to silence the bot complaining about missing 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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530993/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530991/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530998/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530994/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530992/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530997/+files/ProcInterrupts.txt ** Tags removed: apport-collected focal uec-images ** Tags added: regression-proposed -- 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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530996/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945868] Re: focal kvm virtio_net set_features failed (-22)
Hi Markus, thanks for the report. While the good/bad switch with the kernels suggest a reason in there, knowing more about the exact configuration of the guest would help in any case. The reason easily is that myself and million others use virtio-net in focal guests just fine, so there must be some detail to it in your case that makes it differ. Knowing that will help to understand. So let me ask a few clarifications: - You said 20.04 Host, so I assume you are on qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 (could as well be backports and I want to be sure) - You mentioned guest versions, but which exact host kernel version are you using when this happens? - How did you configure your guest and especially the network adapter (libvirt XML if you use it or qemu cmdline if you use some other way to create it) - Does this only apply to an old guest that is kept up (upgrade to 20.04 in the guest, reboot guest, but the qemu process stays since a long time?) or is it reproducible with a freshly started 20.04 guest on the same system? Furthermore let us know if there is more when the issue happens in either of: a) host kernel (dmesg) b) host userspace (qemu log in /var/log/libvirt/guestname) c) guest journal d) host journal From the code that complains in the guest we can check which feature it could not set. The workaround you mentioned was about checksumming, but maybe in your case it is something different. "wanted 0x008000174a29, left 0x00800017ca29" So it wanted to disable one, but could not. This is already interesting as plenty of features are fixed when using virtio-net. You can see that if you look at `$ sudo ethtool --show-features enp1s0` for example. The list your guest request is: tx-scatter-gather tx-checksum-ip-generic highdma rx-vlan-filter tx-generic-segmentation rx-gro tx-tcp-segmentation tx-gso-robust tx-tcp-ecn-segmentation tx-tcp6-segmentation (This is somewhat hard to read, so I hope this is right) But more important is the difference which it wanted to disable but could not. That is 0x8000 which maps via netdev_features_t to "rx-lro" Checking an example guest that I have I see this is default on but should be switchable. This is from the newest Ubuntu release: $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on It might be worth with your working kernel to run the above sequence to see if there it is a) off or on by default on start b) can be turned off/on as requested While you have lost networking after virtio-net fails, it would be even more awesome if you could run the same sequence via e.g. "virsh console" or any other non-network access to the guest that you might have. I was running this sequence then as cross check with Focal host and Focal guest 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I have checked, but LRO is nothing that libvirt/qemu can directly manage [1]. Otherwise I'd have recommended you some of the offloads to tweak there, but as LRO isn't one of them I can't. Summary: - we might need more info to recreate your exact issue - I do not see an issue with 5.4.0-88 as you do. - But I see that something in that exact area changed in 5.4.0-89 in focal-proposed. - I do not get the guest crash that you do with either one. - Even if the above finding isn't your exact issue it might indicate an issue in 5.4.0-89 proposed, I'll split that into a new bug 1946185 to be sure it is seen individually - I can't see anything I could do for qemu here atm (=> incomplete), waiting for the kernel team to have a look [1]: https://libvirt.org/formatdomain.html#setting-nic-driver-specific- options ** Changed in:
[Kernel-packages] [Bug 1946185] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5531001/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5530995/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1946185/+attachment/5531000/+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/1946185 Title: large-receive-offload no more tunable in 5.4.0-89-generic Status in linux package in Ubuntu: Confirmed Bug description: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946185] [NEW] large-receive-offload no more tunable in 5.4.0-89-generic
Public bug reported: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 3. 5.4.0-89-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro on Cannot change large-receive-offload Could not change any device features $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed] $ sudo ethtool --features enp1s0 lro off Cannot change large-receive-offload $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off [fixed I've installed/uninstalled the guest kernel twice but the above behavior remained consistent and seemed to be only influenced by the new kernel. The used guest config is the default that falls out of uvt-kvm, that means in regard to this bug: hvm ... Virt-Stack is qemu 1:4.2-3ubuntu6.17 and libvirt 6.0.0-0ubuntu8.14 from current Focal-updates. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 6 06:47 seq crw-rw 1 root audio 116, 33 Oct 6 06:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=5697bbf9-a186-49b9-98bc-2a94313535b4 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-89-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-focal:cvnQEMU:ct1:cvrpc-q35-focal: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-focal dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: focal regression-proposed ** Tags added: apport-collected focal uec-images ** Description changed: While debugging a bug 1945868 I found something that I think is a separate issue to that original report, hence this new bug. I found the virtio-net behavior changing in an unexpected way in 5.4.0-89-generic that is currently in Focal-proposed. 1. 5.4.0-86-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off 2. 5.4.0-88-generic $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: off $ sudo ethtool --features enp1s0 lro on $ sudo ethtool --show-features enp1s0 | grep large large-receive-offload: on $ sudo ethtool --features enp1s0 lro off $ sudo ethtool --show-features enp1s0 | grep large
[Kernel-packages] [Bug 1946183] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1946183/+attachment/5530976/+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/1946183 Title: [Impish] No HDMI sound (AMD) Status in linux package in Ubuntu: New Bug description: Happens with official Impish 5.13 kernel or 5.15rc from unstable ckt ppa. Video is ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR 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 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946183] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1946183/+attachment/5530974/+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/1946183 Title: [Impish] No HDMI sound (AMD) Status in linux package in Ubuntu: New Bug description: Happens with official Impish 5.13 kernel or 5.15rc from unstable ckt ppa. Video is ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR 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 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946183] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1946183/+attachment/5530981/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946183 Title: [Impish] No HDMI sound (AMD) Status in linux package in Ubuntu: New Bug description: Happens with official Impish 5.13 kernel or 5.15rc from unstable ckt ppa. Video is ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR 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 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946183] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1946183/+attachment/5530980/+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/1946183 Title: [Impish] No HDMI sound (AMD) Status in linux package in Ubuntu: New Bug description: Happens with official Impish 5.13 kernel or 5.15rc from unstable ckt ppa. Video is ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR 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 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
