Re: [Kernel-packages] [Bug 1940780] Re: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04
Find the videos attached, Thank you. Regards, On Wed, Aug 25, 2021 at 5:15 AM Daniel van Vugt <1940...@bugs.launchpad.net> wrote: > Please: > > 1. Tell us the contents of /proc/cmdline > > 2. Attach a video of the problem so we can better understand what you > are seeing. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1940780 > > Title: > [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 > > Status in linux-hwe-5.11 package in Ubuntu: > Incomplete > > Bug description: > Just installed ubuntu 20.04 and the screen has been flickering all > through. tried applying the ubuntu on Wayland solution but no change. > Please help with a solution on workaround for this. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 > Uname: Linux 5.11.0-27-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Aug 22 21:39:46 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170] > InstallationDate: Installed on 2021-08-22 (0 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > MachineType: HP HP EliteBook Folio G1 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic > root=UUID=4b37b99a-c4bf-42ca-9e24-733b7a991c4d ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/19/2016 > dmi.bios.release: 1.10 > dmi.bios.vendor: HP > dmi.bios.version: N91 Ver. 01.10 > dmi.board.name: 8170 > dmi.board.vendor: HP > dmi.board.version: KBC Version 29.68 > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.ec.firmware.release: 41.104 > dmi.modalias: > dmi:bvnHP:bvrN91Ver.01.10:bd07/19/2016:br1.10:efr41.104:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.68:cvnHP:ct10:cvr: > dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI > dmi.product.name: HP EliteBook Folio G1 > dmi.product.sku: Z5Z39US#ABA > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.105-3~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 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/linux-hwe-5.11/+bug/1940780/+subscriptions > > -- *Maina Kelvin Mwangi* ** Attachment added: "Screencast from 08-31-2021 10:40:38 PM.webm" https://bugs.launchpad.net/bugs/1940780/+attachment/5522436/+files/Screencast%20from%2008-31-2021%2010%3A40%3A38%20PM.webm -- 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/1940780 Title: [HP EliteBook Folio G1] Screen keeps flickering on ubuntu 20.04 Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: Just installed ubuntu 20.04 and the screen has been flickering all through. tried applying the ubuntu on Wayland solution but no change. Please help with a solution on workaround for this. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 22 21:39:46 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170] InstallationDate: Installed on 2021-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP EliteBook Folio G1
[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
Alex can you please give this kernel a try: https://people.canonical.com/~khfeng/lp1936708/ -- 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/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them. [Test] Multiple users tested with positive result. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older DP version, this might change the behavior on it. == Original Bug Report == Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3
We get this for free with the move to a 5.13 based focal:linux-intel kernel. ** Changed in: intel Status: New => Invalid ** Changed in: linux-intel (Ubuntu) Status: In Progress => Invalid ** Changed in: intel Assignee: (unassigned) => Brad Figg (brad-figg) ** Changed in: linux-intel (Ubuntu) Assignee: Hsuan-Yu Lin (shanelin) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 Status in intel: Invalid Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Invalid Bug description: Description Enable USB-dw3 for Tiger Lake Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929901] Re: [EHL][TGL] EDAC support
This commit already exists in the focal:linux-intel intel-5.13-next. ** Changed in: intel Status: New => Fix Committed ** Changed in: intel Assignee: (unassigned) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL] EDAC support Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906418] Re: igc driver for Comet Lake onboard 15f3 NIC drops all igmp packets
Marking this fixed, since the problem does not occur with the current kernel for Ubuntu 20.04. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906418 Title: igc driver for Comet Lake onboard 15f3 NIC drops all igmp packets Status in linux package in Ubuntu: Fix Released Bug description: This is occurring on Ubuntu 20.04 with kernel 5.4.0-56-generic. To demonstrate, run $ sudo tcpdump -nv -ienp4s0 igmp (adjusting the interface name appropriately). The result will be 0 packets captured, even though all other Ubuntu systems on the same ethernet lan are reporting igmp queries from the router and responding with reports every minute or so. One consequence of this is that a CUPS server using the Comet Lake onboard ethernet controller cannot be detected by any clients, except within the first 120 seconds after restarting the avahi-daemon. Since the Comet Lake server does not receive the igmp queries, it does not respond with a report and so the router unsubscribes the interface from the multicast group that is used by avahi and bonjour. This makes the CUPS server disappear. The output of ubuntu-bug linux is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: culler 2071 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-17 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. Z490I AORUS ULTRA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=bdba1f28-6903-467f-abfa-10c6bee47cd7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 Tags: focal Uname: Linux 5.4.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6b dmi.board.asset.tag: Default string dmi.board.name: Z490I AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6b:bd11/03/2020:svnGigabyteTechnologyCo.,Ltd.:pnZ490IAORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnZ490IAORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490I AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906418] Re: igc driver for Comet Lake onboard 15f3 NIC drops all igmp packets
You are right! With the 5.11 kernel I am now seeing igmp packets over ethernet. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906418 Title: igc driver for Comet Lake onboard 15f3 NIC drops all igmp packets Status in linux package in Ubuntu: Fix Released Bug description: This is occurring on Ubuntu 20.04 with kernel 5.4.0-56-generic. To demonstrate, run $ sudo tcpdump -nv -ienp4s0 igmp (adjusting the interface name appropriately). The result will be 0 packets captured, even though all other Ubuntu systems on the same ethernet lan are reporting igmp queries from the router and responding with reports every minute or so. One consequence of this is that a CUPS server using the Comet Lake onboard ethernet controller cannot be detected by any clients, except within the first 120 seconds after restarting the avahi-daemon. Since the Comet Lake server does not receive the igmp queries, it does not respond with a report and so the router unsubscribes the interface from the multicast group that is used by avahi and bonjour. This makes the CUPS server disappear. The output of ubuntu-bug linux is attached. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: culler 2071 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-17 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. Z490I AORUS ULTRA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=bdba1f28-6903-467f-abfa-10c6bee47cd7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 Tags: focal Uname: Linux 5.4.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6b dmi.board.asset.tag: Default string dmi.board.name: Z490I AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6b:bd11/03/2020:svnGigabyteTechnologyCo.,Ltd.:pnZ490IAORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnZ490IAORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490I AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940411] Re: 20.04.1 LTS messages after update to linux-firmware_1.187.16_all.deb
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1940411 Title: 20.04.1 LTS messages after update to linux-firmware_1.187.16_all.deb Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hi, running at present 5.11.0-27-generic #29~20.04.1-Ubuntu SMP, after performing apt update, apt upgrade, I get the following warning messages: ... Unpacking linux-firmware (1.187.16) over (1.187.15) ... Setting up linux-firmware (1.187.16) ... update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 ... I'm not sure if my system will boot. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1940411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942377] 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 1942377 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942377 Title: Linux 5.14 fails to boot Status in linux package in Ubuntu: Incomplete Bug description: Downloaded and installed packages of 5.14 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able to boot. Please, look in attachment. Motherboard: Asus P5Q3 CPU: Intel(R) Xeon(R) CPU X5482 OS: Kubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942377] Re: Linux 5.14 fails to boot
A related one on bugzilla (closed as invalid): https://bugzilla.kernel.org/show_bug.cgi?id=214227 -- 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/1942377 Title: Linux 5.14 fails to boot Status in linux package in Ubuntu: Incomplete Bug description: Downloaded and installed packages of 5.14 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able to boot. Please, look in attachment. Motherboard: Asus P5Q3 CPU: Intel(R) Xeon(R) CPU X5482 OS: Kubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942377] [NEW] Linux 5.14 fails to boot
Public bug reported: Downloaded and installed packages of 5.14 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able to boot. Please, look in attachment. Motherboard: Asus P5Q3 CPU: Intel(R) Xeon(R) CPU X5482 OS: Kubuntu 21.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "Trace screenshot" https://bugs.launchpad.net/bugs/1942377/+attachment/5522394/+files/photo_2021-08-30_21-40-47.jpg ** Bug watch added: Linux Kernel Bug Tracker #214227 https://bugzilla.kernel.org/show_bug.cgi?id=214227 -- 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/1942377 Title: Linux 5.14 fails to boot Status in linux package in Ubuntu: Incomplete Bug description: Downloaded and installed packages of 5.14 from https://kernel.ubuntu.com/~kernel-ppa/mainline/ I found it is not able to boot. Please, look in attachment. Motherboard: Asus P5Q3 CPU: Intel(R) Xeon(R) CPU X5482 OS: Kubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
OK, linux-modules was installed but linux-modules-extra was not. I installed that package and booted from 5.11.0-34 and the distortion is back. I removed it, rebooted, and still the distortion was there, but the desktop and network was working. I cannot repeat what happened the first time I booted 5.11.0-34, but it definitely was that version as journalctl --boot=-6 shows it. -- 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/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them. [Test] Multiple users tested with positive result. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older DP version, this might change the behavior on it. == Original Bug Report == Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876990] Re: zfs modules in Focal kernel taint kernel
I'm running into this as well. I'd like to boot the Live CD such that
the kernel is untainted, but since the zfs modules are automatically
loaded, the kernel is tainted at boot.
I was able to ensure that the zfs modules were not loaded at boot by
adding the kernel parameter "systemd.mask=zfs.target" in the grub
bootloader.
I don't think there's a "fix" for this issue, but maybe this will help
someone else running in to this issue.
One thing that would be nice though would be for the kernel parameter
"zfs=(off|no|0)" would disable this target. Just as it disabled module
loading in /etc/initd.d/zfs-import (via /etc/zfs/zfs-functions in
function checksystem).
--
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/1876990
Title:
zfs modules in Focal kernel taint kernel
Status in linux package in Ubuntu:
Won't Fix
Bug description:
the ZFS modules in the shipping focal kernel do not contain the intree
flag, and because of that I believe they are the cause of kernel
tainting discovered during 20.04 certification testing.
The output from a recent certification test run for 20.04:
Kernel taint value is 4097
Taint bit value: 0 (proprietary module was loaded)
Taint bit value: 12 (externally-built ('out-of-tree') module was loaded)
Looking into modinfo for everything loaded at the time, it appears
that the ZFS modules are loaded (even though we did not configure any
ZFS filesystems), and that seems to be the root cause of the test
failure. To test this, I checked /proc/sys/kernel/tainted and
verified it was tainted. I then blacklisted all the ZFS related
modules and rebooted, and then checked /proc/sys/kernel/tainted again
and the kernel no longer shows as being tainted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876990/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942365] [NEW] playing podcast with weird characters in title will trigger error _dbus_check_is_valid_utf8
Public bug reported: playing podcast from phone via BT : Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_playlist_item() 0 Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() Title: electronic drugs�� Sep 1 20:52:00 t-14 bluetoothd[1478227]: dbus[1478227]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. Sep 1 20:52:00 t-14 bluetoothd[1478227]: This is normally a bug in some application using the D-Bus library. Sep 1 20:52:00 t-14 bluetoothd[1478227]: D-Bus not built with -rdynamic so unable to print a backtrace Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() Artist: 3×33: Eternal Bronze Medallists (Bad Voltage) • 8/5/21 Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() Album: Bad Voltage Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() TrackNumber: 0 Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() NumberOfTracks: 5 Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() Genre: Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() Duration: 3273717 Sep 1 20:52:00 t-14 acpid: input device has been disconnected, fd 25 Sep 1 20:52:00 t-14 /usr/lib/gdm3/gdm-x-session[3139]: (II) config/udev: removing device moto g 5G plus (AVRCP) Sep 1 20:52:00 t-14 /usr/lib/gdm3/gdm-x-session[3139]: (**) Option "fd" "135" Sep 1 20:52:00 t-14 /usr/lib/gdm3/gdm-x-session[3139]: (II) event29 - moto g 5G plus (AVRCP): device removed Sep 1 20:52:00 t-14 /usr/lib/gdm3/gdm-x-session[3139]: (II) UnloadModule: "libinput" Sep 1 20:52:00 t-14 /usr/lib/gdm3/gdm-x-session[3139]: (II) systemd-logind: releasing fd for 13:93 Sep 1 20:52:00 t-14 systemd[1]: bluetooth.service: Main process exited, code=dumped, status=6/ABRT Sep 1 20:52:00 t-14 systemd[1]: bluetooth.service: Failed with result 'core-dump'. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 21:04:02 2021 InstallationDate: Installed on 2021-06-28 (65 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20UDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2020 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET58W(1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW 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.27 dmi.modalias: dmi:bvnLENOVO:bvrR1BET58W(1.27):bd10/20/2020:br1.27:efr1.27:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:C9:3D:2D:B9:BD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:132675554 acl:14461701 sco:424673 events:444297 errors:0 TX bytes:317940345 acl:442716 sco:423984 commands:909 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1942365 Title: playing podcast with weird characters in title will trigger error _dbus_check_is_valid_utf8 Status in bluez package in Ubuntu: New Bug description: playing podcast from phone via BT : Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_playlist_item() 0 Sep 1 20:52:00 t-14 bluetoothd[1478227]: profiles/audio/player.c:media_player_set_metadata() Title: electronic drugs�� Sep 1 20:52:00 t-14 bluetoothd[1478227]: dbus[1478227]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. Sep 1 20:52:00 t-14 bluetoothd[1478227]: This is normally a bug in some application
[Kernel-packages] [Bug 1853797] Re: pmu in ubuntu_kvm_unit_tests fails
Found new failures on bionic/linux-oracle/5.4.0-1054.58~18.04.1 on VM.DenseIO2.8 and VM.Standard2.1 2 newly added tests failed 18:12:43 DEBUG| [stdout] FAIL: all counters 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-0 18:12:43 DEBUG| [stdout] PASS: overflow: status-0 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-0 18:12:43 DEBUG| [stdout] PASS: overflow: irq-0 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-1 18:12:43 DEBUG| [stdout] PASS: overflow: status-1 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-1 18:12:43 DEBUG| [stdout] PASS: overflow: irq-1 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-2 18:12:43 DEBUG| [stdout] PASS: overflow: status-2 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-2 18:12:43 DEBUG| [stdout] PASS: overflow: irq-2 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-3 18:12:43 DEBUG| [stdout] PASS: overflow: status-3 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-3 18:12:43 DEBUG| [stdout] PASS: overflow: irq-3 18:12:43 DEBUG| [stdout] PASS: overflow: cntr-4 18:12:43 DEBUG| [stdout] PASS: overflow: status-4 18:12:43 DEBUG| [stdout] PASS: overflow: status clear-4 18:12:43 DEBUG| [stdout] PASS: overflow: irq-4 18:12:43 DEBUG| [stdout] PASS: cmask 18:12:43 DEBUG| [stdout] FAIL: running counter wrmsr: cntr 18:12:43 DEBUG| [stdout] FAIL: running counter wrmsr: status 18:12:43 DEBUG| [stdout] Unhandled exception 13 #GP at ip 0040127f 18:12:43 DEBUG| [stdout] error_code= rflags=00010002 cs=0008 18:12:44 DEBUG| [stdout] rax=00619cf5 rcx=0345 rdx=0002 rbx= 18:12:44 DEBUG| [stdout] rbp=00519f30 rsi=00418117 rdi=00619cf5 18:12:44 DEBUG| [stdout] r8= r9=0020 r10=000d r11=2492492492492493 18:12:44 DEBUG| [stdout] r12=07300402 r13=0603 r14= r15= 18:12:44 DEBUG| [stdout] cr0=80010011 cr2= cr3=01007000 cr4=0020 18:12:44 DEBUG| [stdout] cr8= 18:12:44 DEBUG| [stdout]STACK: @40127f 400338 18:12:44 DEBUG| [stdout] FAIL pmu ** Also affects: linux-oracle-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.4 sru-20210816 -- 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/1853797 Title: pmu in ubuntu_kvm_unit_tests fails Status in ubuntu-kernel-tests: Triaged Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Status in linux-oracle-5.4 package in Ubuntu: New Bug description: 4 failures: FAIL: rdpmc: fixed cntr-0 FAIL: rdpmc: fixed cntr-1 FAIL: rdpmc: fixed cntr-2 FAIL: all counters Test log: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/pmu' BUILD_HEAD=e2c275c4 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 /tmp/tmp.UfviUpwSjB -smp 1 -cpu host # -initrd /tmp/tmp.7jA5GK5kyl enabling apic paging enabled cr0 = 80010011 cr3 = 45a000 cr4 = 20 PMU version: 2 GP counters: 4 GP counter width: 48 Mask length: 7 Fixed counters: 3 Fixed counter width: 48 PASS: core cycles-0 PASS: core cycles-1 PASS: core cycles-2 PASS: core cycles-3 PASS: instructions-0 PASS: instructions-1 PASS: instructions-2 PASS: instructions-3 PASS: ref cycles-0 PASS: ref cycles-1 PASS: ref cycles-2 PASS: ref cycles-3 PASS: llc refference-0 PASS: llc refference-1 PASS: llc refference-2 PASS: llc refference-3 PASS: llc misses-0 PASS: llc misses-1 PASS: llc misses-2 PASS: llc misses-3 PASS: branches-0 PASS: branches-1 PASS: branches-2 PASS: branches-3 PASS: branch misses-0 PASS: branch misses-1 PASS: branch misses-2 PASS: branch misses-3 PASS: fixed-0 PASS: fixed-1 PASS: fixed-2 PASS: rdpmc: cntr-0 PASS: rdpmc: fast-0 PASS: rdpmc: cntr-1 PASS: rdpmc: fast-1 PASS: rdpmc: cntr-2 PASS: rdpmc: fast-2 PASS: rdpmc: cntr-3 PASS: rdpmc: fast-3 FAIL: rdpmc: fixed cntr-0 PASS: rdpmc: fixed fast-0 FAIL: rdpmc: fixed cntr-1 PASS: rdpmc: fixed fast-1 FAIL: rdpmc: fixed cntr-2 PASS: rdpmc: fixed fast-2 FAIL: all counters PASS: overflow: cntr-0 PASS: overflow: status-0 PASS: overflow: status clear-0 PASS: overflow: irq-0 PASS: overflow: cntr-1 PASS: overflow: status-1 PASS: overflow: status clear-1 PASS: overflow: irq-1 PASS: overflow: cntr-2 PASS: overflow: status-2 PASS: overflow: status clear-2 PASS: overflow: irq-2 PASS: overflow: cntr-3 PASS: overflow: status-3 PASS: overflow: status clear-3 PASS: overflow: irq-3
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.11/5.11.0.1015.16~20.04.14)
All autopkgtests for the newly accepted linux-meta-azure-5.11 (5.11.0.1015.16~20.04.14) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
** Changed in: u-boot (Ubuntu Hirsute) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Released Status in u-boot-menu source package in Focal: Fix Released Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Released Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] Fwd: [Bug 1940202] Re: [Dell Inspiron 14-3467] touchpad
thank you to reply -- 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/1940202 Title: [Dell Inspiron 14-3467] touchpad Status in linux package in Ubuntu: Confirmed Bug description: touchpad not work and `` this symbol automatic type then work my pc ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 17 08:16:32 2021 DistUpgraded: 2021-06-27 20:32:09,566 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2020-10-13 (307 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 14-3467 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=0418c796-3730-4ee7-8506-36b30300434a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-27 (50 days ago) dmi.bios.date: 01/13/2021 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.0 dmi.board.name: 0KNKX3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.0:bd01/13/2021:br2.14:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0KNKX3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2 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/1940202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942347] 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 1942347 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/1942347 Title: proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with: 12:48:34 DEBUG| [stdout] proc01 1 TFAIL : proc01.c:400: read failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address I was also able to reproduce this on a amd64 VM running 5.11.0-31-generic by loading the spl module and running: $ sudo cat /proc/sys/kernel/spl/hostid cat: /proc/sys/kernel/spl/hostid: Bad address This is probably not a regression, affecting only s390x now likely because the spl module wasn't loaded on the previous runs. s390x systems are not re-deployed for the regression tests, so this could be a lingering module loaded for previous tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942347] Re: proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute
** Description changed: Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with: 12:48:34 DEBUG| [stdout] proc01 1 TFAIL : proc01.c:400: read failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address + + I was also able to reproduce this on a amd64 VM running + 5.11.0-31-generic by loading the spl module and running: + + $ sudo cat /proc/sys/kernel/spl/hostid + cat: /proc/sys/kernel/spl/hostid: Bad address + + This is probably not a regression, affecting only s390x now likely + because the spl module wasn't loaded on the previous runs. s390x systems + are not re-deployed for the regression tests, so this could be a + lingering module loaded for previous tests. -- 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/1942347 Title: proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Bug description: Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with: 12:48:34 DEBUG| [stdout] proc01 1 TFAIL : proc01.c:400: read failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address I was also able to reproduce this on a amd64 VM running 5.11.0-31-generic by loading the spl module and running: $ sudo cat /proc/sys/kernel/spl/hostid cat: /proc/sys/kernel/spl/hostid: Bad address This is probably not a regression, affecting only s390x now likely because the spl module wasn't loaded on the previous runs. s390x systems are not re-deployed for the regression tests, so this could be a lingering module loaded for previous tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942347] [NEW] proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute
Public bug reported: Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with: 12:48:34 DEBUG| [stdout] proc01 1 TFAIL : proc01.c:400: read failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) 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/1942347 Title: proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Bug description: Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems with: 12:48:34 DEBUG| [stdout] proc01 1 TFAIL : proc01.c:400: read failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
Hi Chris, This one works also but I have this error during boot: [ 1.462530] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. log file is attached Regards Cédric On 9/1/21 10:52 AM, Chris Chiu wrote: > Thanks. Please try > https://people.canonical.com/~mschiu77/lp1941773/f259ee2f0379/ and let > me know the result. Thanks > ** Attachment added: "journal.log" https://bugs.launchpad.net/bugs/1941773/+attachment/5522303/+files/journal.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic
Please help test https://people.canonical.com/~mschiu77/lp1938697/74_117/ and let me know if you can see the second ethernet interface. No need to do apport- collect. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1937133 Title: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Confirmed Bug description: Failing on hirsute/linux 5.11.0-26.28 host s2lp4 Not a regression as this is also failing on 5.11.0-24.25 17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:16:32 DEBUG| [stdout] # Traceback (most recent call last): 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 283, in 17:16:32 DEBUG| [stdout] # main() 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 256, in main 17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 70, in __init__ 17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 64, in get_if_names 17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical': 17:16:32 DEBUG| [stdout] # KeyError: 'flavour' 17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925261] Re: memory leak on AWS kernels when using docker
Paul, The 5.3 kernel you are using is completely unsupported. Until a fix patch is identified for 5.4 your only other choice for supported kernels are to install linux-aws-edge. That package will keep you on a supported kernel through the release of 22.04 (the next LTS). Note, however, that linux-aws-edge will transition you through 3 kernel versions. -- 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/1925261 Title: memory leak on AWS kernels when using docker Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu AMI was released which has the "5.3.0-1032-aws" kernel we have been hitting a 100% repro memory leak that causes our app that is running under docker to be OOM killed. The scenario is that we have an app running in a docker container and it occasionally catches a crash happening within itself and when that happens it creates another process which triggers a gdb dump of that parent app. Normally this works fine but under these specific kernels it causes the memory usage to grow and grow until it hits the maximum allowed memory for the container at which point the container is killed. I have tested using several of the latest available Ubuntu AMIs including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which has the "5.4.0-1045-aws" kernel and the bug still exists. I also tested a bunch of the mainline kernels and found the fix was introduced for this memory leak in the v5.9-rc4 kernel (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES). Do you all have any idea if or when that set of changes will be backported into a supported kernel for Ubuntu 18.04 or 20.04? Release we are running: root@:~# lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 Docker / containerd.io versions: - containerd.io: 1.4.4-1 - docker-ce: 5:20.10.5~3-0~ubuntu-bionic Latest supported kernel I tried which still sees the memory leak: root@hostname:~# apt-cache policy linux-aws linux-aws: Installed: 5.4.0.1045.27 Candidate: 5.4.0.1045.27 Version table: *** 5.4.0.1045.27 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1007.7 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937133] 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 1937133 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937133 Title: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: Failing on hirsute/linux 5.11.0-26.28 host s2lp4 Not a regression as this is also failing on 5.11.0-24.25 17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:16:32 DEBUG| [stdout] # Traceback (most recent call last): 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 283, in 17:16:32 DEBUG| [stdout] # main() 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 256, in main 17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 70, in __init__ 17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 64, in get_if_names 17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical': 17:16:32 DEBUG| [stdout] # KeyError: 'flavour' 17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests fails on hirsute (KeyError: 'flavour')
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Tags added: sru-20210816 ** Summary changed: - devlink_port_split from ubuntu_kernel_selftests fails on hirsute (KeyError: 'flavour') + devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') -- 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/1937133 Title: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: Failing on hirsute/linux 5.11.0-26.28 host s2lp4 Not a regression as this is also failing on 5.11.0-24.25 17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:16:32 DEBUG| [stdout] # Traceback (most recent call last): 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 283, in 17:16:32 DEBUG| [stdout] # main() 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 256, in main 17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 70, in __init__ 17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 64, in get_if_names 17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical': 17:16:32 DEBUG| [stdout] # KeyError: 'flavour' 17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic
No. I will need only the output of "dmesg". You can do "dmesg > dmesg.log" on the 5.4.0-74-generic and attach the dmesg.log here. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.11.0.1015.16)
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1015.16) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934428] Re: Request to pull-in new PERC11 PCI-id from upstream
** Description changed: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: - 1000:00e6:1028:2171 PERC H750 Mini - 1000:00e6:1028:2172 PERC H355 Adapter - 1000:00e6:1028:2173 PERC H355 Front - 1000:00e6:1028:2174 PERC H350 Mini - 1000:00e6:1028:2176 PERC H750 Adapter - 1000:00e6:1028:2177 PERC H350 Adapter + 1000:10e2:1028:2171 PERC H750 Mini + 1000:10e6:1028:2172 PERC H355 Adapter + 1000:10e6:1028:2173 PERC H355 Front + 1000:10e6:1028:2174 PERC H350 Mini + 1000:10e2:1028:2176 PERC H750 Adapter + 1000:10e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:10e2:1028:2171 PERC H750 Mini 1000:10e6:1028:2172 PERC H355 Adapter 1000:10e6:1028:2173 PERC H355 Front 1000:10e6:1028:2174 PERC H350 Mini 1000:10e2:1028:2176 PERC H750 Adapter 1000:10e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900644] Re: tls from net in ubuntu_kernel_selftests failed on G/H/I (multi_chunk_sendfile)
This is fixed for hirsute (checked with linux and linux-riscv) by the following commit: commit 5e7d3d1edcad9b96fe0ddfb155f0109856019f9a Author: Jakub Kicinski Date: Fri Jun 18 13:34:06 2021 -0700 tls: prevent oversized sendfile() hangs by ignoring MSG_MORE BugLink: https://bugs.launchpad.net/bugs/1938340 [ Upstream commit d452d48b9f8b1a7f8152d33ef52cfd7fe1735b0a ] The 5.8 kernels (checked with focal/linux-hwe-5.8) is still affected. But given that the 5.8 kernels are not receiving upstream stable updates anymore this issue will likely not be fixed. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Released ** Also affects: linux-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.8 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-hwe-5.8 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Status: New => Confirmed ** Summary changed: - tls from net in ubuntu_kernel_selftests failed on G/H/I (multi_chunk_sendfile) + tls from net in ubuntu_kernel_selftests failed on G/H (multi_chunk_sendfile) -- 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/1900644 Title: tls from net in ubuntu_kernel_selftests failed on G/H (multi_chunk_sendfile) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux source package in Hirsute: Fix Released Status in linux-hwe-5.8 source package in Hirsute: Invalid Bug description: Issue found on Groovy AWS 5.8.0-1010.10 Test failed with: # [==] Running 93 tests from 4 test cases. # [ RUN ] global.non_established # [ OK ] global.non_established # [ RUN ] global.keysizes # [ OK ] global.keysizes # [ RUN ] tls_basic.base_base # [ OK ] tls_basic.base_base # [ RUN ] tls.12.sendfile # [ OK ] tls.12.sendfile # [ RUN ] tls.12.send_then_sendfile # [ OK ] tls.12.send_then_sendfile # [ RUN ] tls.12.multi_chunk_sendfile # [ FAIL ] tls.12.multi_chunk_sendfile # [ RUN ] tls.12.recv_max # [ OK ] tls.12.recv_max # [ RUN ] tls.12.recv_small # [ OK ] tls.12.recv_small # [ RUN ] tls.12.msg_more # [ OK ] tls.12.msg_more # [ RUN ] tls.12.msg_more_unsent # [ OK ] tls.12.msg_more_unsent # [ RUN ] tls.12.sendmsg_single # [ OK ] tls.12.sendmsg_single # [ RUN ] tls.12.sendmsg_fragmented # [ OK ] tls.12.sendmsg_fragmented # [ RUN ] tls.12.sendmsg_large # [ OK ] tls.12.sendmsg_large # [ RUN ] tls.12.sendmsg_multiple # [ OK ] tls.12.sendmsg_multiple # [ RUN ] tls.12.sendmsg_multiple_stress # [ OK ] tls.12.sendmsg_multiple_stress # [ RUN ] tls.12.splice_from_pipe # [ OK ] tls.12.splice_from_pipe # [ RUN ] tls.12.splice_from_pipe2 # [ OK ] tls.12.splice_from_pipe2 # [ RUN ] tls.12.send_and_splice # [ OK ] tls.12.send_and_splice # [ RUN ] tls.12.splice_to_pipe # [ OK ] tls.12.splice_to_pipe # [ RUN ] tls.12.recvmsg_single # [ OK ] tls.12.recvmsg_single # [ RUN ] tls.12.recvmsg_single_max # [ OK ] tls.12.recvmsg_single_max # [ RUN ] tls.12.recvmsg_multiple # [ OK ] tls.12.recvmsg_multiple # [ RUN ] tls.12.single_send_multiple_recv # [ OK ] tls.12.single_send_multiple_recv # [ RUN ] tls.12.multiple_send_single_recv # [ OK ] tls.12.multiple_send_single_recv # [ RUN ] tls.12.single_send_multiple_recv_non_align # [ OK ] tls.12.single_send_multiple_recv_non_align # [ RUN ] tls.12.recv_partial # [ OK ] tls.12.recv_partial # [ RUN ] tls.12.recv_nonblock # [ OK ] tls.12.recv_nonblock # [ RUN ] tls.12.recv_peek # [ OK ] tls.12.recv_peek # [ RUN ] tls.12.recv_peek_multiple # [ OK ] tls.12.recv_peek_multiple # [ RUN ] tls.12.recv_peek_multiple_records # [ OK ] tls.12.recv_peek_multiple_records # [ RUN ] tls.12.recv_peek_large_buf_mult_recs # [ OK ] tls.12.recv_peek_large_buf_mult_recs # [ RUN ] tls.12.recv_lowat # [ OK ] tls.12.recv_lowat # [ RUN ] tls.12.bidir # [ OK ] tls.12.bidir # [ RUN ] tls.12.pollin # [ OK ] tls.12.pollin # [ RUN ] tls.12.poll_wait # [ OK ] tls.12.poll_wait # [ RUN ] tls.12.poll_wait_split # [ OK ] tls.12.poll_wait_split # [ RUN ] tls.12.blocking # [
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1058.56)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1058.56) for focal have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-5.6 source package in Bionic: Confirmed Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.6 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-5.6 source package in Bionic: Confirmed Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Found on xenial/linux-aws/4.4.0-1132.146 ** Tags added: sru-20210816 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-5.6 source package in Bionic: Confirmed Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Found on xenial/linux-aws/4.4.0-1132.146
** Tags added: 4.4 aws
** Tags added: sru-20210816
--
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/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
I didn't see any other patch that claims to be a fix of this one in
the upstream tree. The problem I think of for the moment is that we
might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation
[Kernel-packages] [Bug 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions)
** Tags added: sru-20210816 -- 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/1821906 Title: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This test has failed on: * T-3.13: - FAIL debug (11 tests, 6 unexpected failures) * T-4.4 / X-4.4: - FAIL debug (13 tests, 1 unexpected failures) Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/debug' BUILD_HEAD=1593e88a timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.eY4ym9tA6e -smp 1 # -initrd /tmp/tmp.FnZA1vIITj enabling apic PASS: reading DR4 with CR4.DE == 0 PASS: reading DR4 with CR4.DE == 1 PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: single step FAIL: single step emulated instructions PASS: hw watchpoint (test that dr6.BS is not cleared) PASS: hw watchpoint (test that dr6.BS is not set) PASS: icebp PASS: MOV SS + watchpoint + ICEBP PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 13 tests, 1 unexpected failures FAIL debug (13 tests, 1 unexpected failures) 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:15:05 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/1821906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
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 in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
I didn't see any other patch that claims to be a fix of this one in
the upstream tree. The problem I think of for the moment is that we
might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error.
[Kernel-packages] [Bug 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions)
Found on xenial/linux-aws/4.4.0-1132.146 ** Tags added: aws ** 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/1821906 Title: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This test has failed on: * T-3.13: - FAIL debug (11 tests, 6 unexpected failures) * T-4.4 / X-4.4: - FAIL debug (13 tests, 1 unexpected failures) Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/debug' BUILD_HEAD=1593e88a timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.eY4ym9tA6e -smp 1 # -initrd /tmp/tmp.FnZA1vIITj enabling apic PASS: reading DR4 with CR4.DE == 0 PASS: reading DR4 with CR4.DE == 1 PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: single step FAIL: single step emulated instructions PASS: hw watchpoint (test that dr6.BS is not cleared) PASS: hw watchpoint (test that dr6.BS is not set) PASS: icebp PASS: MOV SS + watchpoint + ICEBP PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 13 tests, 1 unexpected failures FAIL debug (13 tests, 1 unexpected failures) 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:15:05 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/1821906/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 trusty/linux-aws 4.4.0-1096.101 ** Tags added: trusty -- 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 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
Found on: xenial/linux-aws/4.4.0-1132.146 ** Tags added: 4.4 -- 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 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
** Changed in: linux-azure (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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
** Changed in: linux-azure (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1937078
Title:
Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
Status in linux-azure package in Ubuntu:
Incomplete
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Committed
Bug description:
SRU Justification
[Impact]
Customers have degraded network performance on Hyper-V/Azure
This is a request to pick up a patch from the upstream, the patch
fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
need to get picked up for 20.04, 18.04. The link to the upstream patch
follows:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
fixes=7c9ff3d61b253715dcf968a6307af148c9b2
Description of issue and solution:
The vmbus module uses a rotational algorithm to assign target CPUs to
a device's channels. Depending on the timing of different device's channel
offers, different channels of a device may be assigned to the same CPU.
For example on a VM with 2 CPUs, if NIC A and B's channels are offered
in the following order, NIC A will have both channels on CPU0, and
NIC B will have both channels on CPU1 -- see below. This kind of
assignment causes RSS load that is spreading across different channels
to end up on the same CPU.
Timing of channel offers:
NIC A channel 0
NIC B channel 0
NIC A channel 1
NIC B channel 1
VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
Rel_ID=14, target_cpu=0
Rel_ID=17, target_cpu=0
VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic
network adapter
Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
Rel_ID=16, target_cpu=1
Rel_ID=18, target_cpu=1
Update the vmbus CPU assignment algorithm to avoid duplicate CPU
assignments within a device.
The new algorithm iterates num_online_cpus + 1 times.
The existing rotational algorithm to find "next NUMA & CPU" is still here.
But if the resulting CPU is already used by the same device, it will try
the next CPU.
In the last iteration, it assigns the channel to the next available CPU
like the existing algorithm. This is not normally expected, because
during device probe, we limit the number of channels of a device to
be <= number of online CPUs.
[Test Plan]
This could be tough to test as the patch fixes a race condition.
[Where problems could occur]
Network performance issues could persist.
[Other Info]
SF:#00315347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1058.38)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1058.38) for bionic have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.10.0-1ubuntu1.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) systemd/237-3ubuntu10.51 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) asic0x/1.0.1-1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic
Ok so I tried the modified version. As you'll see the ethernet interface isn't there. I've run apport again. When I switch back to 5.4.0-74-generic from the repo we see the ethernet interface again. Did you want an updated apport from the repo version? -- 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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
# grep CODENAME /etc/os-release VERSION_CODENAME=focal UBUNTU_CODENAME=focal # uname -r 5.11.0-34-generic dmesg: [0.797134] blacklist: Loading compiled-in revocation X.509 certificates [0.797696] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' built-in revocation cert is loaded [0.806069] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [0.806848] integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' mokvar table is available, and is used. # keyctl list %:.blacklist | grep Canonical 613299796: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0 # keyctl list %:.blacklist | grep bin: | wc 79 4748853 # mokutil --list-enrolled --mokx [key 1] [SHA-256] Revoked binaries are correctly loaded from MOKvar table, despite not being mirrored into MokListXRT efi variable. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935778] Re: Request LLVM 12.0.1 backport to focal/updates
** Also affects: llvm-toolchain-12 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: llvm-toolchain-12 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: llvm-toolchain-12 (Ubuntu Focal) Status: New => In Progress ** Changed in: llvm-toolchain-12 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: llvm-toolchain-12 (Ubuntu) Status: New => Fix Released ** Description changed: + [ Impact ] + * People using llvm backend with other compilers + [ Description ] + * There is a fixed bug in 12.0.1 for this issue, the backend is unusable with some external compilers + [ Regression potential ] + * Low, this is part of upstream since 12.0.1 to 14 + [Other info] Hi, Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API that renders it unusable as a backend for some compilers. The upstream commit that fixes the bug is https://github.com/llvm/llvm- project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was included in their 12.0.1 release. Would you be so kind as to backport 12.0.1 to Ubuntu 20.04 LTS, please? Thanks in advance for your reply. ** Summary changed: - Request LLVM 12.0.1 backport to focal/updates + [SRU] Request LLVM 12.0.1 backport to focal/updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-12 in Ubuntu. https://bugs.launchpad.net/bugs/1935778 Title: [SRU] Request LLVM 12.0.1 backport to focal/updates Status in llvm-toolchain-12 package in Ubuntu: Fix Released Status in llvm-toolchain-12 source package in Focal: In Progress Status in llvm-toolchain-12 source package in Hirsute: In Progress Bug description: [ Impact ] * People using llvm backend with other compilers [ Description ] * There is a fixed bug in 12.0.1 for this issue, the backend is unusable with some external compilers [ Regression potential ] * Low, this is part of upstream since 12.0.1 to 14 [Other info] Hi, Focal Fossa currently carries LLVM 12.0.0, which has a bug in its C API that renders it unusable as a backend for some compilers. The upstream commit that fixes the bug is https://github.com/llvm/llvm- project/commit/07234c7d6bc246925710b88a1f9552f678587165 and was included in their 12.0.1 release. Would you be so kind as to backport 12.0.1 to Ubuntu 20.04 LTS, please? Thanks in advance for your reply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1935778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/comments/7 ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942319] [NEW] When booting with UEFI, mokvar table and %:.platform keyring must be available
Public bug reported: When booting with UEFI, mokvar table and %:.platform keyring must be available ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1942319 Title: When booting with UEFI, mokvar table and %:.platform keyring must be available Status in linux-kvm package in Ubuntu: New Bug description: When booting with UEFI, mokvar table and %:.platform keyring must be available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1942319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
# uname -r 5.11.0-34-generic # sudo keyctl list %:.platform 3 keys in keyring: 149920180: ---lswrv 0 0 asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53 434591909: ---lswrv 0 0 asymmetric: Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63 404799886: ---lswrv 0 0 asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4 # sudo keyctl list %:.blacklist | grep bin: | wc 79 4748854 # sudo keyctl list %:.blacklist | grep Canonical 1050199374: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0 dmesg [1.074086] blacklist: Loading compiled-in revocation X.509 certificates [1.074714] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' [1.084216] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [1.085028] integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' MOKvar is available, and used to load Master CA into .platform keyring, and hashes into blacklist keyring. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-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/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/comments/6 ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-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/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. * an ubuntu kernel team regression test is being added to assert that expected revoked certificates have been revoked see https://lists.ubuntu.com/archives/kernel-team/2021-August/122986.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938697] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522250/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522248/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522253/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522256/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522246/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes
[Kernel-packages] [Bug 1938697] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522252/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration:
[Kernel-packages] [Bug 1938697] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522255/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522249/+files/PciMultimedia.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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522251/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration:
[Kernel-packages] [Bug 1938697] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522254/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes
[Kernel-packages] [Bug 1938697] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522247/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522245/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522244/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes
[Kernel-packages] [Bug 1938697] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522241/+files/Card0.Codecs.codec.0.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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration:
[Kernel-packages] [Bug 1938697] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522243/+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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on
[Kernel-packages] [Bug 1938697] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522242/+files/Card0.Codecs.codec.2.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/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration:
[Kernel-packages] [Bug 1938697] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1938697/+attachment/5522240/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938697 Title: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic Status in linux package in Ubuntu: Confirmed Bug description: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes
[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic
apport information ** Description changed: I have found an issue after upgrading my Kernel from 5.4.0-74-generic to 5.4.0-80-generic on Ubuntu 20.04. It appears that support for the second ethernet port on my Lenovo m90n-1 has been dropped or isn't working as expected. After upgrading to 5.4.0-80-generic my second ethernet port Both ethernet ports use the r8169 driver. If I switch back to the previous kernel 5.4.0-74-generic. The second ethernet port is usable again. I did attempt under 5.4.0-80-generic to see if I could get an error message. When the driver attempts to discover the second ethernet port the following error is thrown. "unknown chip XID fcf" Support output below: --- Before update. Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64) root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 1b serial: 98:fa:9b:c9:eb:c7 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff memory:a120-a1203fff --- After update root@lenovo-test-3:~# uname -r 5.4.0-80-generic root@lenovo-test-3:~# lshw -c network *-network DISABLED description: Wireless interface product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlo1 version: 30 serial: 54:8d:5a:ab:41:77 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:a141c000-a141 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 15 serial: 98:fa:9b:c9:eb:c6 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff memory:a130-a1303fff --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-80-generic. AplayDevices: Error: [Errno 2] No such
[Kernel-packages] [Bug 1942316] Re: Touchpad doesn't work at all on Asus TUF Gaming F15 FX506HC-HN007T, after fresh instalation.
Here I attach the output of the following command: cat /proc/bus/input/devices ** Attachment added: "cat /proc/bus/input/devices > ~/devices" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1942316/+attachment/5522238/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942316 Title: Touchpad doesn't work at all on Asus TUF Gaming F15 FX506HC-HN007T, after fresh instalation. Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: 0. Ubuntu version: Ubuntu 18.04.5 LTS 1. Laptop model: Asus TUF Gaming F15 FX506HC-HN007T 2. Touchpad manufacturer: Unknown 3. The problem started right after installing ubuntu, I realised it when I was selecting the language the touchpad did not work at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 12:55:35 2021 InstallationDate: Installed on 2021-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1942316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942316] [NEW] Touchpad doesn't work at all on Asus TUF Gaming F15 FX506HC-HN007T, after fresh instalation.
Public bug reported: 0. Ubuntu version: Ubuntu 18.04.5 LTS 1. Laptop model: Asus TUF Gaming F15 FX506HC-HN007T 2. Touchpad manufacturer: Unknown 3. The problem started right after installing ubuntu, I realised it when I was selecting the language the touchpad did not work at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 12:55:35 2021 InstallationDate: Installed on 2021-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1942316 Title: Touchpad doesn't work at all on Asus TUF Gaming F15 FX506HC-HN007T, after fresh instalation. Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: 0. Ubuntu version: Ubuntu 18.04.5 LTS 1. Laptop model: Asus TUF Gaming F15 FX506HC-HN007T 2. Touchpad manufacturer: Unknown 3. The problem started right after installing ubuntu, I realised it when I was selecting the language the touchpad did not work at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 12:55:35 2021 InstallationDate: Installed on 2021-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1942316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
Verifying using hirsute: # uname -r 5.11.0-1014-kvm # grep CODENAME /etc/os-release VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute # keyctl list %:.blacklist Can't find 'keyring:.blacklist' Upgraded kernel: # uname -r 5.11.0-1015-kvm # keyctl list %:.blacklist 1 key in keyring: 330780907: ---lswrv 0 0 asymmetric: Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0 In dmesg: [0.375674] blacklist: Loading compiled-in revocation X.509 certificates [0.376015] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing: 61482aa2830d0ab2ad5af10b7250da9033ddcef0' No other blacklist hashes got imported, cause they do not appear in mokvar table nor in MokListRT mirror variable, nor does kvm kernel appear to have platform keyring... which is very odd cause UEFI db keys for Microsoft Production PCA 2011 and UEFI CA 2011 are missing. It seems to me that kvm kernel is a bit broken, and doesn't have support for mokvar or .platform keyring, which is very bad. -- 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/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
Disabled initrd less boot, and installing linux-generic kernel from 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/1928679 Title: Support importing mokx keys into revocation list from the mok table Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx) which revokes many Ubuntu kernel hashes and 2012 signing key. * Kernel should import those into it's %:.blacklist keyring such that it prohibits signed kexec of the revoked kernels. * v5.13-rc1 kernel has learned how to import mokx and how to import full certs into the %:.blacklist keyring. * However, it only does so by reading MokListXRT efi variable. * Due to the large size of Ubuntu's vendor-dbx, shim does not create MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2 MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also exposes MokListXRT via mokvar table, which is easier to parse and contains all the revocations in full. Kernel needs a patch to read MokListXRT via mokvar table. * We have two options on how to proceed from here, either we include the same hashes and certs as our vendordbx in in the kernel as revocation list, or we fix kernel to read MokListXRT via mokvar table * The above is known as CVE-2020-26541 * Separately it would be nice to add informational dmesg messages when revoking signing certificates, as a good indication that signing key rotation events have happened and have been applied correctly. [Test Plan] * Boot kernel with 15.4 based Ubuntu shim * Install keyutils package * Execute $ sudo keyctl list %:.blacklist it should list in exccess of 300+ hash entries. It also must list assymetric Canonical signing key from 2012. * Separately check dmesg to observe that asymmetric canonical signing key from 2012 is revoked. [Where problems could occur] * EFI variable storage can be full thus preventing shim to mirror efivars and the moktable. On decent hardware this should not happen, but has been observed to be corrupted on some older EDKII based OVMF instances with small EFI variable storage space (pre-4MB). [Other Info] * The patches to fix the above have been submitted upstream https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/ https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/ This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE kernel, until accepted upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942092] Re: linux-azure: main(): sched_setscheduler(): Operation not permitted
This bug is awaiting verification that the 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-azure-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1942092 Title: linux-azure: main(): sched_setscheduler(): Operation not permitted Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.11 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: New Status in linux-azure-5.8 package in Ubuntu: New Status in linux-azure source package in Trusty: New Status in linux-azure-4.15 source package in Trusty: Invalid Status in linux-azure-5.11 source package in Trusty: Invalid Status in linux-azure-5.4 source package in Trusty: Invalid Status in linux-azure-5.8 source package in Trusty: Invalid Status in linux-azure source package in Xenial: New Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-azure-5.11 source package in Xenial: Invalid Status in linux-azure-5.4 source package in Xenial: Invalid Status in linux-azure-5.8 source package in Xenial: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: New Status in linux-azure-5.11 source package in Bionic: Invalid Status in linux-azure-5.4 source package in Bionic: New Status in linux-azure-5.8 source package in Bionic: Invalid Status in linux-azure source package in Focal: New Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: New Status in linux-azure-5.4 source package in Focal: Invalid Status in linux-azure-5.8 source package in Focal: New Status in linux-azure source package in Hirsute: New Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-azure-5.4 source package in Hirsute: Invalid Status in linux-azure-5.8 source package in Hirsute: Invalid Bug description: [Impact] We have several regressions with RT and ADT with the azure kernels. The tests seem to fail when calling sched_setscheduler() or with related operations. This was probably introduced by LP:#1939024 that enabled CONFIG_RT_GROUP_SCHED. We should revert this change until we better understand the impact it can cause. * ubuntu_ltp_stable The ltp syscall regression test is failing for all the azure kernels with: main(): sched_setscheduler(): Operation not permitted http://10.246.75.167/2021.08.16/hirsute/linux- azure/5.11.0-1014.15/sru-azure-azure-Standard_A2_v2-ubuntu_ltp_stable- log.txt * ubuntu_qrt_apparmor Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' * systemd ADT (Hirsute) https://autopkgtest.ubuntu.com/results/autopkgtest- hirsute/hirsute/amd64/s/systemd/20210827_233206_a2599@/log.gz [Test Plan] The kernel should pass the regression and adt tests. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1942092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1057.55)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1057.55) for focal have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share
When will this be fixed? Not fixed in 20.04
--
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/1572132
Title:
SMBv2+ does not show all files when mounting a windows share
Status in Linux:
Unknown
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Fix Released
Bug description:
When using the SMBv2 Protocol to mount a top level windows share (such
as C:\) not all files (or directories) are shown that exist on the
server side. Exactly 2 files are always missing...
Steps to reproduce:
On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top
level share - a subfolder like C:\data\ seems to work)
sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0
As a result always 2 Files (or directories) are missing in the mounted
directory of the ubuntu installation.
Seems to be a kernel bug (source tree: linux/fs/cifs).
The ubuntu versions I have checked:
Ubuntu 14.04LTS amd64
Ubuntu 15.10 amd64
Ubuntu 16.04 amd64
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.12
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Tue Apr 19 14:50:02 2016
InstallationDate: Installed on 2016-04-19 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160417.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1572132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic
Hello alex dekker, have you installed also linux-modules-5.11.0-34-generic and linux- modules-extra-5.11.0-34-generic? -- 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/1936708 Title: Wobbly graphics on built-in display since linux- image-5.11.0-22-generic Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: == SRU Justification == [Impact] Wobbly graphics after a kernel update. [Fix] Older panels may require more bandwidth then advertised, so we need to use max params for them. [Test] Multiple users tested with positive result. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older DP version, this might change the behavior on it. == Original Bug Report == Lenovo laptop with Intel + Nvidia graphics. Since booting from linux-image-5.11.0-22-generic, the built-in display is unusable, with wobbling horizontal stripes from the disk decryption prompt onwards: https://www.youtube.com/watch?v=LyRTuPzCe2I HDMI output works fine. If I boot from linux-image-5.11.0-18-generic instead, all is well. If I use Recovery mode with linux-image-5.11.0-22-generic and continue bootup, it's usable but there's no HDMI output. I think others may be having this issue too: https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base# ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1598 F pulseaudio /dev/snd/controlC0: alex 1598 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 17 09:50:31 2021 InstallationDate: Installed on 2021-01-03 (194 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 80DU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago) dmi.bios.date: 08/18/2014 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN31WW(V1.14) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y70-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y70-70 Touch dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 80DU dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch dmi.product.version: Lenovo Y70-70 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.8/5.8.0.65.47)
All autopkgtests for the newly accepted linux-meta-hwe-5.8 (5.8.0.65.47) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-65.73 (ppc64el, s390x, amd64, arm64) evdi/1.9.1-1ubuntu4~20.04.1 (ppc64el) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.8 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1057.37)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1057.37) for bionic have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.10.0-1ubuntu1.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) asic0x/1.0.1-1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
5.13.0-1011-oem #15-Ubuntu SMP Fri Aug 27 09:45:09 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
[6.954194] ath10k_pci :03:00.0: No hardware memory
[6.954197] ath10k_pci :03:00.0: failed to copy target iram contents: -12
[6.985209] ath10k_pci :04:00.0: No hardware memory
[6.985213] ath10k_pci :04:00.0: failed to copy target iram contents: -12
[7.060527] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.106011] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
works
** 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.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
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 Hirsute:
In Progress
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.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[4.463156]
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
Thanks. Please try https://people.canonical.com/~mschiu77/lp1941773/f259ee2f0379/ and let me know the result. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933566] Re: XPS 9510 (TGL) Screen Brightness could not be changed
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1933566
Title:
XPS 9510 (TGL) Screen Brightness could not be changed
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
Kernel 5.12+ support the backlight via:
commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1933566/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
I didn't see any other patch that claims to be a fix of this one in
the upstream tree. The problem I think of for the moment is that we
might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11
[Kernel-packages] [Bug 1821390] Re: apic-split will fail in kvm_units_tests
Still visible on H-kvm 5.11.0-1015.16 ** Tags added: sru-20210816 -- 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/1821390 Title: apic-split will fail in kvm_units_tests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split 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/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd /tmp/tmp.ZHQwPUOuLD qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id PASS: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: PASS: apic_disable: Local apic enabled in xAPIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: 1050014 PASS: apic_disable: *0xfee00080: 0 PASS: apic_disable: *0xfee00080: f0 PASS: apic_disable: Local apic enabled in x2APIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: x2apic enabled to disabled state PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand FAIL: PV IPIs testing PASS: nmi-after-sti PASS: multiple nmi PASS: APIC LVT timer one shot starting apic change mode PASS: TMICT value reset PASS: TMCCT should have a non-zero value PASS: TMCCT should have reached 0 PASS: TMCCT should have a non-zero value PASS: TMCCT should not be reset to TMICT value PASS: TMCCT should be reset to the initial-count PASS: TMCCT should not be reset to init PASS: TMCCT should have reach zero PASS: TMCCT should stay at zero PASS: tsc deadline timer PASS: tsc deadline timer clearing SUMMARY: 51 tests, 1 unexpected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
So "focal-proposed" offers me the update "linux-image-5.11.0-34-generic"
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
[7.234159] ath10k_pci :03:00.0: failed to copy target iram contents: -12
[7.242923] ath10k_pci :04:00.0: failed to copy target iram contents: -12
[7.291070] ath10k_pci :03:00.0: could not init core (-12)
[7.291076] ath10k_pci :03:00.0: could not probe fw (-12)
[7.299146] ath10k_pci :04:00.0: could not init core (-12)
[7.299169] ath10k_pci :04:00.0: could not probe fw (-12)
it was clear that the patch is not in the kernel and thanks for wasting my time.
Without concrete information I test nothing at all.
--
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/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
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 Hirsute:
In Progress
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.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
[Kernel-packages] [Bug 1938143] Re: Include product_sku info to modalias
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1938143 Title: Include product_sku info to modalias Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] When we add DMI quirks for the new platforms, it's hard to prevent from leaking its model name. Our customer doesn't like it. [Fix] Introduce the product sku modalias to DMI table, so that we can use more meaningless product sku string to match the platform. [Test] No real DMI quirk is added in this commit, so need to do any tests. [Where problems could occur] It's safe to add one more DMI entry, nothing could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1938143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939915] Re: memory leaking when removing a profile
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1939915
Title:
memory leaking when removing a profile
Status in AppArmor:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
There's a memory leak in the kernel when removing a profile.
A simple reproducible example:
root@ubuntu:~# echo "profile foo {}" > profile
root@ubuntu:~# apparmor_parser profile
root@ubuntu:~# apparmor_parser -R profile
root@ubuntu:~# echo scan > /sys/kernel/debug/kmemleak
root@ubuntu:~# cat /sys/kernel/debug/kmemleak
unreferenced object 0x99bcf5128bb0 (size 16):
comm "apparmor_parser", pid 1318, jiffies 4295139856 (age 33.196s)
hex dump (first 16 bytes):
01 00 00 00 00 00 00 00 98 1f 01 fd bc 99 ff ff
backtrace:
[] kmem_cache_alloc_trace+0xd8/0x1e0
[<86ca7bd9>] aa_alloc_proxy+0x30/0x60
[<0e34f34c>] aa_alloc_profile+0xd4/0x100
[] unpack_profile+0x16f/0xe10
[<19033e2b>] aa_unpack+0x119/0x500
[] aa_replace_profiles+0x94/0xca0
[<1833f520>] policy_update+0x124/0x1e0
[<992f950e>] profile_load+0x7d/0xa0
[] __vfs_write+0x1b/0x40
[<4e709f5d>] vfs_write+0xb9/0x1a0
[<280db840>] SyS_write+0x5e/0xe0
[<14c5ab5d>] do_syscall_64+0x79/0x130
[] entry_SYSCALL_64_after_hwframe+0x41/0xa6
[<9d368497>] 0x
This issue was already fixed upstream 3622ad25d4d6 v5.8-rc1~102^2
It still needs to be applied on xenial, bionic and focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1939915/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942295] Re: [nouveau] Xorg freeze / crashes with Dual GPU. 20.04/21.04
As I said the proprietary drivers don't work either on either 20.04 or 21.04. I will try to do another install and switch to the proprietary for another bug report shortly. I don't think there are any errors with the proprietary though, the system is just unusable if you enable the primary GPU screens. -- 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/1942295 Title: [nouveau] Xorg freeze / crashes with Dual GPU. 20.04/21.04 Status in linux package in Ubuntu: Confirmed Bug description: This is a rather huge issue and I'm not 100% if it's xorg or a kernel issue. I have tons of errors from the DE, Nouveau drivers and various other things. In 16.04.X and 18.04.X everything has worked fine. When I tried to upgrade to 20.04 setting up my screens either locks the machine up and causes all sorts of crazy issues (crashes pretty much anything that draws to screen). Testing 21.04.3 the issue persists. Issues also don't care if I'm running nouveau or proprietary, it merely changes various problems. [ 14.405062] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 14.948769] nouveau :26:00.0: DRM: wndw-0: timeout [ 16.954561] nouveau :26:00.0: DRM: core notifier timeout [ 18.954601] nouveau :26:00.0: DRM: wndw-2: timeout [ 20.960380] nouveau :26:00.0: DRM: core notifier timeout [ 22.960428] nouveau :26:00.0: DRM: wndw-4: timeout [ 52.803952] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 52.853329] nouveau :26:00.0: DRM: core notifier timeout ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.461 CompositorRunning: None CurrentDesktop: XFCE Date: Wed Sep 1 06:28:49 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] NVIDIA Corporation TU116 [GeForce GTX 1660] [10de:2184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660] [19da:5543] LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd MS-7C02 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 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/1942295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1937991] Re: Skip rtcpie test in kselftests/timers if the default RTC device does not exist
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1937991 Title: Skip rtcpie test in kselftests/timers if the default RTC device does not exist Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [Impact] This test will require /dev/rtc0, the default RTC device, or one specified by user to run. Since this default RTC is not guaranteed to exist on all of the devices, so check its existence first, otherwise skip this test with the kselftest skip code 4. Without this patch this test will fail like this on a s390x zVM: $ selftests: timers: rtcpie $ /dev/rtc0: No such file or directory not ok 1 selftests: timers: rtcpie # exit=22 We have this test disabled in our test suite with an if check [1], thus we're not seeing this failure recently. With this patch applied we can remove that code block later. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client- tests.git/tree/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py#n133 [Fix] * 0d3e5a057992bd selftests: timers: rtcpie: skip test if default RTC device does not exist [Test] Run this test with patched source tree on a s390x zVM and it will be skipped correctly: $ selftests: timers: rtcpie $ Default RTC /dev/rtc0 does not exist. Test Skipped! not ok 9 selftests: timers: rtcpie # SKIP [Where problems could occur] If this fix is incorrect we might see it failing again on systems that without /dev/rtc0 (after removing our local hacks in autotest-client-tests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942295] 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/1942295 Title: [nouveau] Xorg freeze / crashes with Dual GPU. 20.04/21.04 Status in linux package in Ubuntu: Confirmed Bug description: This is a rather huge issue and I'm not 100% if it's xorg or a kernel issue. I have tons of errors from the DE, Nouveau drivers and various other things. In 16.04.X and 18.04.X everything has worked fine. When I tried to upgrade to 20.04 setting up my screens either locks the machine up and causes all sorts of crazy issues (crashes pretty much anything that draws to screen). Testing 21.04.3 the issue persists. Issues also don't care if I'm running nouveau or proprietary, it merely changes various problems. [ 14.405062] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 14.948769] nouveau :26:00.0: DRM: wndw-0: timeout [ 16.954561] nouveau :26:00.0: DRM: core notifier timeout [ 18.954601] nouveau :26:00.0: DRM: wndw-2: timeout [ 20.960380] nouveau :26:00.0: DRM: core notifier timeout [ 22.960428] nouveau :26:00.0: DRM: wndw-4: timeout [ 52.803952] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 52.853329] nouveau :26:00.0: DRM: core notifier timeout ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.461 CompositorRunning: None CurrentDesktop: XFCE Date: Wed Sep 1 06:28:49 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] NVIDIA Corporation TU116 [GeForce GTX 1660] [10de:2184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660] [19da:5543] LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd MS-7C02 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 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/1942295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
With 4.4.0-214.246~14.04.1 it will timeout Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/apic' BUILD_HEAD=1593e88a timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ShWgkBXugG -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.33CAVckrXS enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 1007000 cr4 = 20 apic version: 14 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic disabled FAIL: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: apic_disable: *0xfee00030: FAIL: apic_disable: CR8: f PASS: apic_disable: CR8: f FAIL: apic_disable: *0xfee00080: f0 KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: apic_disable: Local apic enabled in xAPIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: 50014 PASS: apic_disable: *0xfee00080: 0 PASS: apic_disable: *0xfee00080: f0 KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: apic_disable: Local apic enabled in x2APIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) FAIL: apic_disable: *0xfee00030: 50014 FAIL: apic_disable: CR8: f KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: apic_disable: CR8: f FAIL: apic_disable: *0xfee00080: f0 x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: x2apic enabled to disabled state KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic disabled to apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self_ipi_xapic: Local apic enabled in xAPIC mode PASS: self_ipi_xapic: self ipi KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: self_ipi_x2apic: Local apic enabled in x2APIC mode PASS: self_ipi_x2apic: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) SKIP: PV IPIs testing: h-call not available KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: nmi-after-sti KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) ... KVM: injection failed, MSI lost (Operation not permitted) KVM: injection failed, MSI lost (Operation not permitted) PASS: multiple nmi PASS: pending nmi PASS: APIC LVT timer one shot starting apic change mode PASS: TMICT value reset PASS: TMCCT should
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
Spotted on T-4.4 4.4.0-214.246~14.04.1 ** Tags added: sru-20210816 -- 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/1748103 Title: apic test in kvm-unit-test failed with timeout Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-azure-edge source package in Bionic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /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/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: sru-20210816 -- 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 1821906] Re: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4
** Description changed: This test has failed on: - * T-3.13: - - FAIL debug (11 tests, 6 unexpected failures) - * T-4.4 / X-4.4: - - FAIL debug (11 tests, 1 unexpected failures) + * T-3.13: + - FAIL debug (11 tests, 6 unexpected failures) + * T-4.4 / X-4.4: + - FAIL debug (13 tests, 1 unexpected failures) root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=debug TIMEOUT=90s ACCEL= ./x86/run x86/debug.flat -smp 1 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/debug.flat -smp 1 # -initrd /tmp/tmp.WOQmQkB7bo enabling apic PASS: #BP PASS: hw breakpoint (test that dr6.BS is not set) PASS: hw breakpoint (test that dr6.BS is not cleared) PASS: single step FAIL: single step emulated instructions PASS: hw watchpoint (test that dr6.BS is not cleared) PASS: hw watchpoint (test that dr6.BS is not set) PASS: icebp PASS: MOV SS + watchpoint + ICEBP PASS: MOV SS + watchpoint + int $1 PASS: MOV SS + watchpoint + INT3 SUMMARY: 11 tests, 1 unexpected failures 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:15:05 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: This test has failed on: * T-3.13: - FAIL debug (11 tests, 6 unexpected failures) * T-4.4 / X-4.4: - FAIL debug (13 tests, 1 unexpected failures) - root@gonzo:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=debug TIMEOUT=90s ACCEL= ./x86/run x86/debug.flat -smp 1 - 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/debug.flat -smp 1 # -initrd /tmp/tmp.WOQmQkB7bo - enabling apic - PASS: #BP - PASS: hw breakpoint (test that dr6.BS is not set) - PASS: hw breakpoint (test that dr6.BS is not cleared) - PASS: single step - FAIL: single step emulated instructions - PASS: hw watchpoint (test that dr6.BS is not cleared) - PASS: hw watchpoint (test that dr6.BS is not set) - PASS: icebp - PASS: MOV SS + watchpoint + ICEBP - PASS: MOV SS + watchpoint + int $1 - PASS: MOV SS + watchpoint + INT3 - SUMMARY: 11 tests, 1 unexpected failures + Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/debug' + BUILD_HEAD=1593e88a + timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.eY4ym9tA6e -smp 1 # -initrd /tmp/tmp.FnZA1vIITj + enabling apic + PASS: reading DR4 with CR4.DE == 0 + PASS: reading DR4 with CR4.DE == 1 + PASS: #BP + PASS: hw breakpoint (test that dr6.BS is not set) + PASS: hw breakpoint (test that dr6.BS is not cleared) + PASS: single step + FAIL: single step emulated instructions + PASS: hw watchpoint (test that dr6.BS is not cleared) + PASS: hw watchpoint (test that dr6.BS is not set) + PASS: icebp + PASS: MOV SS + watchpoint + ICEBP + PASS: MOV SS + watchpoint + int $1 + PASS: MOV SS + watchpoint + INT3 + SUMMARY: 13 tests, 1 unexpected failures + FAIL debug (13 tests, 1 unexpected failures) + 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:15:05 2019 SourcePackage: linux-signed-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 + debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions) -- 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/1821906 Title: debug in ubuntu_kvm_unit_test failed on 3.13 / 4.4 (FAIL: single step emulated instructions) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This test has failed on: * T-3.13: - FAIL debug (11 tests, 6 unexpected failures) * T-4.4 / X-4.4: - FAIL debug (13 tests, 1 unexpected failures)
[Kernel-packages] [Bug 1942295] Re: Xorg freeze / crashes with Dual GPU. 20.04/21.04
The kernel log messages shown here are a bug in the nouveau driver, which is not well supported. We recommend using the 'Additional Drivers' app to install one of the proprietary Nvidia drivers instead. If those cause "various problems" as you say then please open a separate bug about them. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Xorg freeze / crashes with Dual GPU. 20.04/21.04 + [nouveau] Xorg freeze / crashes with Dual GPU. 20.04/21.04 ** Tags added: nouveau -- 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/1942295 Title: [nouveau] Xorg freeze / crashes with Dual GPU. 20.04/21.04 Status in linux package in Ubuntu: New Bug description: This is a rather huge issue and I'm not 100% if it's xorg or a kernel issue. I have tons of errors from the DE, Nouveau drivers and various other things. In 16.04.X and 18.04.X everything has worked fine. When I tried to upgrade to 20.04 setting up my screens either locks the machine up and causes all sorts of crazy issues (crashes pretty much anything that draws to screen). Testing 21.04.3 the issue persists. Issues also don't care if I'm running nouveau or proprietary, it merely changes various problems. [ 14.405062] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 14.948769] nouveau :26:00.0: DRM: wndw-0: timeout [ 16.954561] nouveau :26:00.0: DRM: core notifier timeout [ 18.954601] nouveau :26:00.0: DRM: wndw-2: timeout [ 20.960380] nouveau :26:00.0: DRM: core notifier timeout [ 22.960428] nouveau :26:00.0: DRM: wndw-4: timeout [ 52.803952] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 52.853329] nouveau :26:00.0: DRM: core notifier timeout ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.461 CompositorRunning: None CurrentDesktop: XFCE Date: Wed Sep 1 06:28:49 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] NVIDIA Corporation TU116 [GeForce GTX 1660] [10de:2184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660] [19da:5543] LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd MS-7C02 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 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
[Kernel-packages] [Bug 1942299] Re: On booting Lubuntu impish daily - cd/dvd tray ejects
I booted the same media on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) no ejecting of CD/DVD tray on boot. -- 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/1942299 Title: On booting Lubuntu impish daily - cd/dvd tray ejects Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu impish daily boot on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) This daily was booted more than once, on each boot, just prior to plymouth screen appearing the cd/dvd tray would be ejected. If my installation media was on the cd/dvd - would that have crashed install? I've been noting this behavior on my primary box - dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) each day (Ubuntu impish, ubuntu, xubuntu & lubuntu desktops installed; occurs when Xfce or LXQt is running.. I don't think I've tried suspend with GNOME with 5.13 kernel) when I resume it in the morning (I suspend each night), likely the 11 days since `uptime` says I last rebooted (I tend to reboot only about once per fortnight) ** actual results On booting daily; the CD/DVD tray ejects ** expected results The CD/DVD is not being used on this boot; I'd expect the tray to remain as it was ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-14-generic 5.13.0-14.14 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1602 F pulseaudio /dev/snd/controlC1: lubuntu1602 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt Date: Wed Sep 1 07:03:31 2021 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210831) MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-14-generic N/A linux-backports-modules-5.13.0-14-generic N/A linux-firmware 1.199 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2010 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:sku:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
** Summary changed:
- kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
+ kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
--
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/1932966
Title:
kvm_unit_tests: emulator test fails on 4.4 / 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
I didn't see any other patch that claims to be a fix of this one in
the upstream tree. The problem I think of for the moment is that we
might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error.
[Kernel-packages] [Bug 1939225] Re: supervisor read write access in kernel mode
** Attachment added: "error7.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939225/+attachment/5522162/+files/error7.txt -- 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/1939225 Title: supervisor read write access in kernel mode Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: There was a null pointer error. I attached the error log from journal control. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 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 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 09:54:04 2021 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/1939225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942299] Re: On booting Lubuntu impish daily - cd/dvd tray ejects
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1942299 ** Tags added: iso-testing -- 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/1942299 Title: On booting Lubuntu impish daily - cd/dvd tray ejects Status in linux package in Ubuntu: Confirmed Bug description: Lubuntu impish daily boot on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) This daily was booted more than once, on each boot, just prior to plymouth screen appearing the cd/dvd tray would be ejected. If my installation media was on the cd/dvd - would that have crashed install? I've been noting this behavior on my primary box - dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) each day (Ubuntu impish, ubuntu, xubuntu & lubuntu desktops installed; occurs when Xfce or LXQt is running.. I don't think I've tried suspend with GNOME with 5.13 kernel) when I resume it in the morning (I suspend each night), likely the 11 days since `uptime` says I last rebooted (I tend to reboot only about once per fortnight) ** actual results On booting daily; the CD/DVD tray ejects ** expected results The CD/DVD is not being used on this boot; I'd expect the tray to remain as it was ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-14-generic 5.13.0-14.14 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1602 F pulseaudio /dev/snd/controlC1: lubuntu1602 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt Date: Wed Sep 1 07:03:31 2021 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210831) MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.13.0-14-generic N/A linux-backports-modules-5.13.0-14-generic N/A linux-firmware 1.199 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2010 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:sku:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942295] [NEW] Xorg freeze / crashes with Dual GPU. 20.04/21.04
You have been subscribed to a public bug: This is a rather huge issue and I'm not 100% if it's xorg or a kernel issue. I have tons of errors from the DE, Nouveau drivers and various other things. In 16.04.X and 18.04.X everything has worked fine. When I tried to upgrade to 20.04 setting up my screens either locks the machine up and causes all sorts of crazy issues (crashes pretty much anything that draws to screen). Testing 21.04.3 the issue persists. Issues also don't care if I'm running nouveau or proprietary, it merely changes various problems. [ 14.405062] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 14.948769] nouveau :26:00.0: DRM: wndw-0: timeout [ 16.954561] nouveau :26:00.0: DRM: core notifier timeout [ 18.954601] nouveau :26:00.0: DRM: wndw-2: timeout [ 20.960380] nouveau :26:00.0: DRM: core notifier timeout [ 22.960428] nouveau :26:00.0: DRM: wndw-4: timeout [ 52.803952] nouveau :26:00.0: disp: outp 04:0006:0f41: training failed [ 52.853329] nouveau :26:00.0: DRM: core notifier timeout ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.461 CompositorRunning: None CurrentDesktop: XFCE Date: Wed Sep 1 06:28:49 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] [19da:1438] NVIDIA Corporation TU116 [GeForce GTX 1660] [10de:2184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU116 [GeForce GTX 1660] [19da:5543] LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd MS-7C02 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.H5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 TOMAHAWK (MS-7C02) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H5:bd04/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd:pnMS-7C02:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB450TOMAHAWK(MS-7C02):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C02 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute ubuntu -- Xorg freeze / crashes with Dual GPU. 20.04/21.04 https://bugs.launchpad.net/bugs/1942295 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
