[Kernel-packages] [Bug 1886744] Re: Enable Quectel EG95 LTE modem [2c7c:0195]
** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem-5.6 (Ubuntu Bionic) ** No longer affects: linux-oem-5.6 (Ubuntu Eoan) ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/1886744 Title: Enable Quectel EG95 LTE modem [2c7c:0195] Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] No modems were found by `mmcli -L` [Fix] Below 2 commits are required to enable this chip. https://lkml.org/lkml/2020/7/7/200 https://lkml.org/lkml/2020/7/7/199 [Test] Verified on the machine with EG95 LTE modem [Regression Potential] Low, just adding IDs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card
Please just test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ -- 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/1810416 Title: SD card error mmc0: error -110 whilst initialising SD card Status in linux package in Ubuntu: Confirmed Bug description: When inserting card to internal card reader: laurynas@laurynas-ThinkPad-T450:~$ dmesg [342809.333716] mmc0: error -110 whilst initialising SD card laurynas@laurynas-ThinkPad-T450:~$ uname -a Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux SanDisk Extreme 64GB UHS 3. Working fine on windows 10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: laurynas 3963 F pulseaudio /dev/snd/controlC0: laurynas 3963 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jan 3 16:09:26 2019 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4 InstallationDate: Installed on 2017-02-18 (683 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20BUS3GN07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JBET68WW (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS3GN07 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS3GN07 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I think it means 59,94Hz, which's available on Linux too. And okey, I'll do it, thank you Kai-Heng! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version:
[Kernel-packages] [Bug 1887620] [NEW] nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-40-generic Date: Thu Jul 9 06:16:55 2020 Dependencies: InstallationDate: Installed on 2020-05-28 (47 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 440.100-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887620 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-40-generic Date: Thu Jul 9 06:16:55 2020 Dependencies: InstallationDate: Installed on 2020-05-28 (47 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 440.100-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-kernel-source-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] [NEW] Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
Public bug reported: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887622] [NEW] Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
Public bug reported: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887622 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] Re: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
cat version.log Ubuntu 5.4.0-40.44-generic 5.4.44 dpkg -l | grep linux-firmware ii linux-firmware 1.187.1 all Firmware for Linux kernel drivers -- 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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887124 Title: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification: == [Impact] * DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally, in case one activates either zfcp DIF (data integrity field) or DIX (data integrity extention) and attaches any LU. * zfcp used to allocate/add the shost object for a HBA, before knowing all the HBA's capabilities. But later the shost object got patched to make more of the capabilities known - including the protection capabilities. * Changes that are later made to the protection capabilities don't get reflected in the tag-set requests and are missing. * Now sending I/O, scsi_mod tries to access the protection payload data, that isn't there, and the kernel crashes. [Fix] * The SRU request was created as pull request, so please pull starting at 0b38938af911 to head / 9227405ee311 from https://code.launchpad.net/~fheimes/+git/lp1887124 [Test Case] * Have a IBM Z or LInuxONE system (ideally on LPAR) in place that is connected to a DS8xxx storage subsystem that supports, zfcp SCSI storage with DIF and DIX. * Have an Ubuntu Server 20.04 installed in such a LPAR system. * Now enable DIF (zfcp.dif=1) or DIX (zfcp.dix=1) and connect the system to a logical unit. * Monitor the system for any kernel crashes (/var/log/syslog and /var/log/kern.log) - look for kernel panic in scsi_queue_rq. [Regression Potential] * Even if the modifications are substantial, the regression potnetial can be considered as moderate. * This issue could be mainly tracked down to commit '737eb78e82d5' (made for v5.4) that made the problem more visible. * With the old blk queue DIF/DIX worked fine, but after scsi_mod switched to blk-mq (and because requests are now all allocated during allocation time of the blk-mq tag-set), it didn't worked anymore. * The solution is to allocate/add the shost object for a HBA after all of its base capabilities are known. * Since the situation is like this for quite a while, several places in the zfcp driver code (where it's assumed that the shost object was correctly allocated) needed to be touched. * This is finally the reason (as well as the fact that some parts depend on code that went upstream with the kernels 5.5 and 5.7) for this rather big patchset for fixing DIF and DIX support in zfcp. * On the other hand side this entire set is now upstream accepted and entirely included in 5.8 (and with that soon in groovy), and no 5.4-specific (hand-crafted) backports are needed. * Also notice that all modifications are in the zfcp driver layer, hence they are s390x specific, and with that limited to /drivers/s390/scsi/zfcp_* * Finally the patches were already tested with a patched focal kernel with DIF/DIX/NONE, with I/O, and local/remote cable pulls - switched and point-to-point connected. No regressions were identified. [Other] * Alternatively the patches can also be cherry-picked from linux master with: git cherry-pick 92953c6e0aa7~1..e76acc519426 git cherry-pick a3fd4bfe85fb git cherry-pick e05a10a05509~1..42cabdaf103b git cherry-pick cec9cbac5244 git cherry-pick 978857c7e367~1..d0dff2ac98dd * The following lists the individual commits - just for the reason of completeness: * 92953c6e0aa77d4febcca6dd691e8192910c8a28 92953c6e0aa77 "scsi: zfcp: signal incomplete or error for sync exchange config/port data" * 7e418833e68948cb9ed15262889173b7db2960cb 7e418833e6894 "scsi: zfcp: diagnostics buffer caching and use for exchange port data" * 088210233e6fc039fd2c0bfe44b06bb94328d09e 088210233e6fc "scsi: zfcp: add diagnostics buffer for exchange config data" * a10a61e807b0a226b78e2041843cbf0521bd0c35 a10a61e807b0a "scsi: zfcp: support retrieval of SFP Data via Exchange Port Data" * 6028f7c4cd87cac13481255d7e35dd2c9207ecae 6028f7c4cd87c "scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver" * 8155eb0785279728b6b2e29aba2ca52d16aa526f 8155eb0785279 "scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs" * 5a2876f0d1ef26b76755749f978d46e4666013dd 5a2876f0d1ef2 "scsi: zfcp: introduce sysfs interface to read the local B2B-Credit" * 8a72db70b5ca3c3feb3ca25519e8a9516cc60cfe 8a72db70b5ca3 "scsi
[Kernel-packages] [Bug 1887623] Re: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887622] Re: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
*** This bug is a duplicate of bug 1887623 *** https://bugs.launchpad.net/bugs/1887623 ** This bug has been marked a duplicate of bug 1887623 Atheros QCA9377 WiFi Not detected on Ubuntu 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/1887622 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880519] Re: System stops responding while entering S3 with SD card installed
** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- 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/1880519 Title: System stops responding while entering S3 with SD card installed Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Won't Fix Status in linux-oem source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: Triaged Status in linux-oem source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [SRU Justfication] [Impact] The system stops responding while entering S3, screen will be lit up if touchpad is triggered by finger. Cursor could be seen with black background, but system is not responding to any input. [Fix] b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM f0c472a6da51 xhci: Return if xHCI doesn't support LPM [Fix] Patchset[1] for fix this issue currently landed in upstream, so we backported them: [1]: b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM f0c472a6da51 xhci: Return if xHCI doesn't support LPM [Test] With the above patch applied, run: sudo fwts --s3-sleep-delay=30 --s3-multiple=30 -p s3 Can passed 30 times. [Regression Potential] Low, the patch is just like a safeguard, doesn't really change any behavior. [Reproduce Steps] 1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso 2. Upgrade kernel to 4.15.0-1080-oem 3. Boot the system with 4.15.0-1080-oem kernel 4. Insert SD card 5. Suspend the system to S3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.laun
[Kernel-packages] [Bug 1886744] Re: Enable Quectel EG95 LTE modem [2c7c:0195]
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1886744 Title: Enable Quectel EG95 LTE modem [2c7c:0195] Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] No modems were found by `mmcli -L` [Fix] Below 2 commits are required to enable this chip. https://lkml.org/lkml/2020/7/7/200 https://lkml.org/lkml/2020/7/7/199 [Test] Verified on the machine with EG95 LTE modem [Regression Potential] Low, just adding IDs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] 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 1887623 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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly
I've been examining the zfs_arc_max setting to see if this can stabilize
the I/O performance. You may like to try setting this as a proportion of
your available memory to see if it improves things. For example, with a
machine with 8GB of memory, I set this to 2GB and my test system went
from being able to reproduce your issue to one where the I/O performance
remained constant for hundreds of fio tests.
For example, to set 2GB arc max use:
echo 2147483648 | sudo tee /sys/module/zfs/parameters/zfs_arc_max
sync
echo 3 | sudo tee /proc/sys/vm/drop_caches
If it is set too low it impacts on cache hits and this reduces I/O
rates. If it is set too high you hit the issue you are seeing because
of cache contention between ZFS and the block layer. I suspect the only
way to find the sweet spot for your use case is with some careful
experimentation. Don't rely on synthetic tests to set this, real world
I/O patterns are best to use for this kind of tuning.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883676
Title:
ZFS performance drops suddenly
Status in zfs-linux package in Ubuntu:
Incomplete
Bug description:
Run Phoronix Flexible IO / Random write benchmark.
After running the benchmark repeatedly multiple times (occasionally it can be
30 minutes or 8 hours), the performance drops suddenly. The only way (I know
of) to get back to high performance is reboot.
---
$ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" |
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops;
done
$ less /tmp/iops
...
2095
2095
2093
783
388
389
...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.9
ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
Uname: Linux 5.3.0-1023-aws x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Tue Jun 16 08:55:01 2020
Ec2AMI: ami-06fd83ae47b05282f
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1f
Ec2InstanceType: c4.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1883676/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Here you go Nicolas ** Attachment added: "dmesg 5.4.42 kernel.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392768/+files/dmesg%205.4.42%20kernel.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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 C
[Kernel-packages] [Bug 1885271] Re: kernel oops xr-usb-serial
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100&id=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Found in a post on Reddit, a workaround that worked for me via GUI. Even though this is still a bug I wanted to help this workaround get more exposure. ``` Just installed 20.04. Same issue. But i have a workaround that doesn't involve manual settings with xrandr. If i set them so that all monitors align at the bottom, it works as expected. This makes for a bit of wonky cursor movement screen-to- screen, but it's usable for now until it gets fixed. Something about the nvdidia driver seems to not be able to map the position to any other configuration. It does not work if for me if I align them all at the top, only with them all aligned at the bottom. Source: https://www.reddit.com/r/pop_os/comments/g7pwq8/multimonitor_screen_rotation_not_working_in_2004/ ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Invalid Status in mutter source package in Focal: In Progress Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A ve
[Kernel-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
@Hui, how do you create those entries? You shouldn't have to deal with the spacing if you use e.g 'dch -i' to update the changelog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845860] Re: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.)
Test passed with Bionic 5.3 Oracle -- 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/1845860 Title: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Issue found on 5.3 Bionic hwe: Running './test_maps' libbpf: BTF is required, but is missing or corrupted. Failed to load SK_SKB verdict prog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic
The GPU falling off bus, in this case, looks like something that is hardware specific, not necessarily related to the change in this SRU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1884060 Title: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 source package in Bionic: Confirmed Bug description: SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 435 NVIDIA driver (nvidia-graphics-drivers-435_435.21-0ubuntu0.18.04.3). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only backport fixes that are already in more recent stable Ubuntu releases. __ Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/nvidia-graphics-drivers-435/20200617_180544_6a91a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884060] Re: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic
I don't think this should block the SRU. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1884060 Title: nvidia-graphics-drivers-435 435.21-0ubuntu0.18.04.2 ADT test failure with 5.4 kernels in Bionic Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 source package in Bionic: Confirmed Bug description: SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 435 NVIDIA driver (nvidia-graphics-drivers-435_435.21-0ubuntu0.18.04.3). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only backport fixes that are already in more recent stable Ubuntu releases. __ Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/nvidia-graphics-drivers-435/20200617_180544_6a91a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1884060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
** Tags added: sru-20200629 -- 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/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-gke package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: New Bug description: This test will attempt to insert the test_bpf module, but this module does not exist in KVM kernels: $ sudo modprobe test_bpf modprobe: FATAL: Module test_bpf not found in directory /lib/modules/4.15.0-1028-kvm The script: $ sudo ./test_bpf.sh test_bpf: [FAIL] $ cat test_bpf.sh #!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Runs bpf test using test_bpf kernel module if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi This test_bpf module will need the CONFIG_TEST_BPF to be enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 08:29:29 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
** Also affects: linux-oracle (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/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-gke package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: New Bug description: This test will attempt to insert the test_bpf module, but this module does not exist in KVM kernels: $ sudo modprobe test_bpf modprobe: FATAL: Module test_bpf not found in directory /lib/modules/4.15.0-1028-kvm The script: $ sudo ./test_bpf.sh test_bpf: [FAIL] $ cat test_bpf.sh #!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Runs bpf test using test_bpf kernel module if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi This test_bpf module will need the CONFIG_TEST_BPF to be enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 08:29:29 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3
Found on B-5.4 oracle 5.4.0-1021.21~18.04.1 ** Tags added: sru-20200629 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1851619 Title: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: The test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp) # selftests: net: test_blackhole_dev.sh # test_blackhole_dev: [FAIL] not ok 13 selftests: net: test_blackhole_dev.sh Need to run this manually to see what's going on there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
** Tags added: oracle sru-20200629 -- 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/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Bug description: This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Please run `watch -n0 cat /proc/interrupts`, put finger on the touchpad and see "AMDI0010:03", "pinctrl_amd" or "MSFT0001:00" increase the interrupt count rapidly. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: ski
[Kernel-packages] [Bug 1887623] Re: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
apport information ** Tags added: apport-collected ** Description changed: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: poonam 1564 F pulseaudio + /dev/snd/controlC0: poonam 1564 F pulseaudio + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-07-13 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: + lono wireless extensions. + + enp2s0no wireless extensions. + MachineType: Dell Inc. Inspiron 5575 + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-40-generic N/A + linux-backports-modules-5.4.0-40-generic N/A + linux-firmware1.187.1 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: focal + Uname: Linux 5.4.0-40-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: 10/31/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.3.3 + dmi.board.asset.tag: not specified + dmi.board.name: 0M0Y6P + dmi.board.vendor: Dell Inc. + dmi.board.version: X01 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.3.3 + dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5575 + dmi.product.sku: 0812 + dmi.product.version: 1.3.3 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392773/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-g
[Kernel-packages] [Bug 1887623] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392778/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392774/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392784/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392775/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392787/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392777/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392782/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392781/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392786/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392783/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392776/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392779/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392780/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392785/+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/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887623] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1887623/+attachment/5392788/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887623 Title: Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
I thought the results above would be sufficient, here is the full output: sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: AT Translated Set 2 keyboard /dev/input/event3: Video Bus /dev/input/event4: Video Bus /dev/input/event5: PixArt USB Optical Mouse /dev/input/event6: Integrated Camera: Integrated C /dev/input/event7: Ideapad extra buttons /dev/input/event8: Elan Touchpad /dev/input/event9: HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10 Select the device event number [0-15]: 2 Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x1 product 0x1 version 0xab83 Input device name: "AT Translated Set 2 keyboard" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 2 (KEY_1) Event code 3 (KEY_2) Event code 4 (KEY_3) Event code 5 (KEY_4) Event code 6 (KEY_5) Event code 7 (KEY_6) Event code 8 (KEY_7) Event code 9 (KEY_8) Event code 10 (KEY_9) Event code 11 (KEY_0) Event code 12 (KEY_MINUS) Event code 13 (KEY_EQUAL) Event code 14 (KEY_BACKSPACE) Event code 15 (KEY_TAB) Event code 16 (KEY_Q) Event code 17 (KEY_W) Event code 18 (KEY_E) Event code 19 (KEY_R) Event code 20 (KEY_T) Event code 21 (KEY_Y) Event code 22 (KEY_U) Event code 23 (KEY_I) Event code 24 (KEY_O) Event code 25 (KEY_P) Event code 26 (KEY_LEFTBRACE) Event code 27 (KEY_RIGHTBRACE) Event code 28 (KEY_ENTER) Event code 29 (KEY_LEFTCTRL) Event code 30 (KEY_A) Event code 31 (KEY_S) Event code 32 (KEY_D) Event code 33 (KEY_F) Event code 34 (KEY_G) Event code 35 (KEY_H) Event code 36 (KEY_J) Event code 37 (KEY_K) Event code 38 (KEY_L) Event code 39 (KEY_SEMICOLON) Event code 40 (KEY_APOSTROPHE) Event code 41 (KEY_GRAVE) Event code 42 (KEY_LEFTSHIFT) Event code 43 (KEY_BACKSLASH) Event code 44 (KEY_Z) Event code 45 (KEY_X) Event code 46 (KEY_C) Event code 47 (KEY_V) Event code 48 (KEY_B) Event code 49 (KEY_N) Event code 50 (KEY_M) Event code 51 (KEY_COMMA) Event code 52 (KEY_DOT) Event code 53 (KEY_SLASH) Event code 54 (KEY_RIGHTSHIFT) Event code 55 (KEY_KPASTERISK) Event code 56 (KEY_LEFTALT) Event code 57 (KEY_SPACE) Event code 58 (KEY_CAPSLOCK) Event code 59 (KEY_F1) Event code 60 (KEY_F2) Event code 61 (KEY_F3) Event code 62 (KEY_F4) Event code 63 (KEY_F5) Event code 64 (KEY_F6) Event code 65 (KEY_F7) Event code 66 (KEY_F8) Event code 67 (KEY_F9) Event code 68 (KEY_F10) Event code 69 (KEY_NUMLOCK) Event code 70 (KEY_SCROLLLOCK) Event code 71 (KEY_KP7) Event code 72 (KEY_KP8) Event code 73 (KEY_KP9) Event code 74 (KEY_KPMINUS) Event code 75 (KEY_KP4) Event code 76 (KEY_KP5) Event code 77 (KEY_KP6) Event code 78 (KEY_KPPLUS) Event code 79 (KEY_KP1) Event code 80 (KEY_KP2) Event code 81 (KEY_KP3) Event code 82 (KEY_KP0) Event code 83 (KEY_KPDOT) Event code 85 (KEY_ZENKAKUHANKAKU) Event code 86 (KEY_102ND) Event code 87 (KEY_F11) Event code 88 (KEY_F12) Event code 89 (KEY_RO) Event code 90 (KEY_KATAKANA) Event code 91 (KEY_HIRAGANA) Event code 92 (KEY_HENKAN) Event code 93 (KEY_KATAKANAHIRAGANA) Event code 94 (KEY_MUHENKAN) Event code 95 (KEY_KPJPCOMMA) Event code 96 (KEY_KPENTER) Event code 97 (KEY_RIGHTCTRL) Event code 98 (KEY_KPSLASH) Event code 99 (KEY_SYSRQ) Event code 100 (KEY_RIGHTALT) Event code 102 (KEY_HOME) Event code 103 (KEY_UP) Event code 104 (KEY_PAGEUP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 107 (KEY_END) Event code 108 (KEY_DOWN) Event code 109 (KEY_PAGEDOWN) Event code 110 (KEY_INSERT) Event code 111 (KEY_DELETE) Event code 112 (KEY_MACRO) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 117 (KEY_KPEQUAL) Event code 118 (KEY_KPPLUSMINUS) Event code 119 (KEY_PAUSE) Event code 121 (KEY_KPCOMMA) Event code 122 (KEY_HANGUEL) Event code 123 (KEY_HANJA) Event code 124 (KEY_YEN) Event code 125 (KEY_LEFTMETA) Event code 126 (KEY_RIGHTMETA) Event code 127 (KEY_COMPOSE) Event code 128 (KEY_STOP) Event code 140 (KEY_CALC) Event code 142 (KEY_SLEEP) Event code 143 (KEY_WAKEUP) Event code 155 (KEY_MAIL) Event code 156 (KEY_BOOKMARKS)
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
AMDI0010:03 and pinctrl_amd are present but the count does not move when I move finger or click on the touchpad. Please note I tried to remove my USB Mouse which is responsible for the high counts on one of xhci_hcd. For this mouse it's moving rapidly. Two screen captures enclosed. ** Attachment added: "Capture d’écran de 2020-07-15 13-39-38.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392808/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-07-15%2013-39-38.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLEN
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Attachment added: "Capture d’écran de 2020-07-15 13-46-14.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392809/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-07-15%2013-46-14.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ub
[Kernel-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
I use 'dch -i' and choose emacs as the editor, after open the changelog, the emacs is in the c-language mode. If I press enter to start a new line, the emacs will automatically change the whitespace to the "TAB", then I need to manually change the "TAB" back to whitespace, but I thought there are 2 whitespace before email line. So the main root cause is my emacs's configuration is not correct, and the 2nd cause is I thought there are 2 whitespace. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392822/+files/dmesg -- 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/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN54WW:bd06/13/2017:svnLENOVO:pn80NV:pvrLenovoideapadY700-15ISK:rvnLENOVO:rnAllsparks5A:rvrSDK0J40709WIN:cvnLENOVO:
[Kernel-packages] [Bug 1886744] Re: Enable Quectel EG95 LTE modem [2c7c:0195]
** Tags added: newparis oem-priority originate-from-1886146 -- 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/1886744 Title: Enable Quectel EG95 LTE modem [2c7c:0195] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] No modems were found by `mmcli -L` [Fix] Below 2 commits are required to enable this chip. https://lkml.org/lkml/2020/7/7/200 https://lkml.org/lkml/2020/7/7/199 [Test] Verified on the machine with EG95 LTE modem [Regression Potential] Low, just adding IDs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: iproute2 (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: iproute2 (Ubuntu Bionic) Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884805] [NEW] The system doesn't power down
You have been subscribed to a public bug: step to reproduce is very simple $poweroff the desktop quits, the screen goes black but the computer never shutdown last lines from journalctl are juin 23 16:20:10 pc1 systemd[1]: Reached target Shutdown. juin 23 16:20:10 pc1 systemd[1]: Reached target Final Step. juin 23 16:20:10 pc1 systemd[1]: systemd-poweroff.service: Succeeded. juin 23 16:20:10 pc1 systemd[1]: Finished Power-Off. juin 23 16:20:10 pc1 systemd[1]: Reached target Power-Off. juin 23 16:20:10 pc1 systemd[1]: Shutting down. juin 23 16:20:10 pc1 systemd-shutdown[1]: Syncing filesystems and block devices. juin 23 16:20:10 pc1 systemd-shutdown[1]: Sending SIGTERM to remaining processes... juin 23 16:20:10 pc1 systemd-journald[407]: Journal stopped ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 17:37:52 2020 InstallationDate: Installed on 2014-06-03 (2211 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. H61M-D2-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=6081a4ec-8716-452d-98c2-c59ace5a96b7 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-21 (32 days ago) dmi.bios.date: 03/27/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: H61M-D2-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61M-D2-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- The system doesn't power down https://bugs.launchpad.net/bugs/1884805 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] [NEW] Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
You have been subscribed to a public bug: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2020-06-19 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. GL552VW NonfreeKernelModules: nvidia_modeset nvidia Package: xserver-xorg-video-intel 2:2.99.917+git20200226-1 PackageArchitecture: amd64 Pr
[Kernel-packages] [Bug 1884726] Re: [TTM] Buffer eviction failed
Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ If the issue persists, please file an upstream bug at https://gitlab.freedesktop.org/drm/nouveau/issues ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884726 Title: [TTM] Buffer eviction failed Status in linux package in Ubuntu: Incomplete Bug description: Under some usage conditions on Ubuntu 20.04 I get an almost complete system freeze and after some minutes I get this issuing a dmesg command: "[TTM] Buffer eviction failed". I can always reproduce the problem using Streetview function inside maps.google.com using Firefox (77.0.1). My kernel version is 5.4.0-38 and my graphic card is an old Nvidia 01:00.0 VGA compatible controller: NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1 When I switch to closed source Nvidia proprietary driver (ver. 340.108) I have no issues. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michele1586 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=4e56d43d-0da0-4af9-a55c-035f04c115bf InstallationDate: Installed on 2017-11-13 (952 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire 5720 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-38-generic root=UUID=28547816-80be-43c8-a86e-d655d7d8ad5e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-38-generic N/A linux-backports-modules-5.4.0-38-generic N/A linux-firmware1.187.1 StagingDrivers: ashmem_linux Tags: focal staging Uname: Linux 5.4.0-38-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (60 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 11/10/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.45 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Nettiling dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.45 dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5720:pvrV1.45:rvnAcer:rnNettiling:rvrV1.45:cvnAcer:ct1:cvrV1.45: dmi.product.family: None dmi.product.name: Aspire 5720 dmi.product.sku: None dmi.product.version: V1.45 dmi.sys.vendor: Acer modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2019-08-08T12:13:15.951541 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] [NEW] Introduce the new NVIDIA 450-server and the 450 UDA series
Public bug reported: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Package changed: nvidia-graphics-drivers-440 (Ubuntu) => nvidia- graphics-drivers-450 (Ubuntu) ** Also affects: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884805] Re: The system doesn't power down
** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884805 Title: The system doesn't power down Status in linux package in Ubuntu: Confirmed Bug description: step to reproduce is very simple $poweroff the desktop quits, the screen goes black but the computer never shutdown last lines from journalctl are juin 23 16:20:10 pc1 systemd[1]: Reached target Shutdown. juin 23 16:20:10 pc1 systemd[1]: Reached target Final Step. juin 23 16:20:10 pc1 systemd[1]: systemd-poweroff.service: Succeeded. juin 23 16:20:10 pc1 systemd[1]: Finished Power-Off. juin 23 16:20:10 pc1 systemd[1]: Reached target Power-Off. juin 23 16:20:10 pc1 systemd[1]: Shutting down. juin 23 16:20:10 pc1 systemd-shutdown[1]: Syncing filesystems and block devices. juin 23 16:20:10 pc1 systemd-shutdown[1]: Sending SIGTERM to remaining processes... juin 23 16:20:10 pc1 systemd-journald[407]: Journal stopped ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 17:37:52 2020 InstallationDate: Installed on 2014-06-03 (2211 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. H61M-D2-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=6081a4ec-8716-452d-98c2-c59ace5a96b7 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-21 (32 days ago) dmi.bios.date: 03/27/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: H61M-D2-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61M-D2-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Ok, there are four refreshes for 1920x1080: 1920x1080 60.00*+ 59.97 59.96 59.93 What if different one get picked? ** No longer affects: nouveau-firmware (Ubuntu) ** No longer affects: mesa (Ubuntu) ** No longer affects: nvidia-graphics-drivers-440 (Ubuntu) ** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** No longer affects: xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driv
[Kernel-packages] [Bug 1884805] 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/1884805 Title: The system doesn't power down Status in linux package in Ubuntu: Confirmed Bug description: step to reproduce is very simple $poweroff the desktop quits, the screen goes black but the computer never shutdown last lines from journalctl are juin 23 16:20:10 pc1 systemd[1]: Reached target Shutdown. juin 23 16:20:10 pc1 systemd[1]: Reached target Final Step. juin 23 16:20:10 pc1 systemd[1]: systemd-poweroff.service: Succeeded. juin 23 16:20:10 pc1 systemd[1]: Finished Power-Off. juin 23 16:20:10 pc1 systemd[1]: Reached target Power-Off. juin 23 16:20:10 pc1 systemd[1]: Shutting down. juin 23 16:20:10 pc1 systemd-shutdown[1]: Syncing filesystems and block devices. juin 23 16:20:10 pc1 systemd-shutdown[1]: Sending SIGTERM to remaining processes... juin 23 16:20:10 pc1 systemd-journald[407]: Journal stopped ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 23 17:37:52 2020 InstallationDate: Installed on 2014-06-03 (2211 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. H61M-D2-B3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=6081a4ec-8716-452d-98c2-c59ace5a96b7 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-21 (32 days ago) dmi.bios.date: 03/27/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: H61M-D2-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61M-D2-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
The patch author wants to know if upstream stable 5.5 has the same issue. The kernel can be found here: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.19/ -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 00
[Kernel-packages] [Bug 1887595] Re: linux-firmware: integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines
This bug was fixed in the package linux-firmware - 1.189 --- linux-firmware (1.189) groovy; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git f39b68729aab3787b89c35bbbd76538e3edb13c4 - QCA: Update WCN3991 FW files - amdgpu: add UVD firmware for SI asics - QCA: Update Bluetooth firmware for QCA6390 - linux-firmware: wilc1000: add wilc1000 v15.4 FW - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - Update binary firmware for MT7663 based devices to include firmware offload feature and low power feature. * Revert the sof-firmware and tplg files from v0.6_release for tgl machines (LP: #1885970) - SAUCE: Revert "UBUNTU: SAUCE: add sof firmware and tplg for tgl platforms" * Integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines (LP: #1887595) - SAUCE: integrate TGL_SOF_FW_prod_signed_v0.6.2_release -- Seth Forshee Wed, 15 Jul 2020 08:03:03 -0500 ** Changed in: linux-firmware (Ubuntu Groovy) Status: New => Fix Released -- 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/1887595 Title: linux-firmware: integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] There is no sof-firmware for tgl platforms in the focal and groovy, so the audio driver can't work on the tgl machines. [Fix] Intel released a firmware for tgl platforms, it is signed by production key. [Test Case] Install the TGL_SOF_FW_prod_signed_v0.6.2_release to /lib/firmware/intel/sof, boot the dell tgl machines, the sof driver loads the sof-firmware successfully, and the audio driver works well too. [Regression Risk] Low, this SRU adds new firmware, this firmware is only used by intel tgl machines, and Intel told us this firmware is signed by production key and is ok to release to ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885970] Re: linux-firmware: revert the sof-firmware and tplg files from v0.6_release for tgl machines
This bug was fixed in the package linux-firmware - 1.189 --- linux-firmware (1.189) groovy; urgency=medium * Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git f39b68729aab3787b89c35bbbd76538e3edb13c4 - QCA: Update WCN3991 FW files - amdgpu: add UVD firmware for SI asics - QCA: Update Bluetooth firmware for QCA6390 - linux-firmware: wilc1000: add wilc1000 v15.4 FW - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - Update binary firmware for MT7663 based devices to include firmware offload feature and low power feature. * Revert the sof-firmware and tplg files from v0.6_release for tgl machines (LP: #1885970) - SAUCE: Revert "UBUNTU: SAUCE: add sof firmware and tplg for tgl platforms" * Integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines (LP: #1887595) - SAUCE: integrate TGL_SOF_FW_prod_signed_v0.6.2_release -- Seth Forshee Wed, 15 Jul 2020 08:03:03 -0500 ** Changed in: linux-firmware (Ubuntu Groovy) Status: New => Fix Released -- 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/1885970 Title: linux-firmware: revert the sof-firmware and tplg files from v0.6_release for tgl machines Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] We integrated the sof-firmware and tplg for tgl platforms. But recently Intel told us this firmware is not signed by production key, we need to revert it. [Fix] Revert the firmware and tplg [Test Case] ls /lib/firmware/intel/sof/ ls /lib/firmware/intel/sof-tplg/ [Regression Risk] Low, just revert a patch we just merged last cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1885970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
This bug also affects my laptop touchpad Lenvo Legion 5-ARH05 5.7.1 Kernel https://linux-hardware.org/?probe=d449a0b248 -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRel
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
I believe the mention pre-req patch is actually wrong (or not quite the patch we would be looking for). Instead commit 6e8634eb13f30c58d1e28d975d99509680e1abc3 Author: Roman Mashak Date: Thu Mar 29 18:12:35 2018 -0400 tc: add oneline mode Add initial support for oneline mode in tc; actions, filters and qdiscs will be gradually updated in the follow-up patches. Signed-off-by: Roman Mashak Signed-off-by: David Ahern Adds the local declaration and assignment (the assignment is still in there after moving the declaration with the other patch). The magic there is that _SL_ is "\\" if set into oneline mode and otherwise "\n". However since oneline is not yet supported in the 18.04 version, I would propose to just adjust the fix with a declaration of _SL_ = "\n" in tc/tc.c. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
5.5.19 looks good for me. I have home over nfs4+krb5p, so the original bug triggers immediately after login and the DE locks up. The problem mentioned in comment #31 is not really reproducible, I only encountered it on the first few boots on Monday, the patched 5.4.0-40 has been stable yesterday and today for my use case. -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
I would like to verify any changes before moving ahead with SRU. But the given instructions are incomplete or at least not generically usable. Could the instructions be updated with steps that can be performed in a generic VM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403282] Re: General protection fault on c->freelist broken with Trusty Tahr
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: New => 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/1403282 Title: General protection fault on c->freelist broken with Trusty Tahr Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [6650285.515240] CPU: 15 PID: 27439 Comm: vtep_test.sh Tainted: GW 3.13.0-34-generic #60-Ubuntu [6650285.525760] Hardware name: Cisco Systems Inc UCSC-C220-M3S/UCSC-C220-M3S, BIOS C220M3.1.5.4f.0.111320130449 11/13/2013 [6650285.537933] task: 883fa972c7d0 ti: 8830372a6000 task.ti: 8830372a6000 [6650285.546506] RIP: 0010:[] [] kmem_cache_alloc_trace+0x80/0x1f0 [6650285.556815] RSP: 0018:8830372a7e80 EFLAGS: 00010286 [6650285.562990] RAX: RBX: 883f3a2178c0 RCX: 01bf16c6 [6650285.571235] RDX: 01bf16c5 RSI: 80d0 RDI: 881fff803500 [6650285.579477] RBP: 8830372a7eb8 R08: 000172a0 R09: 881fff803500 [6650285.587721] R10: 811c5b6e R11: 0246 R12: 00060006 [6650285.595962] R13: 80d0 R14: 0280 R15: 881fff803500 [6650285.604211] FS: 7fe3cf4ec740() GS:88407fce() knlGS: [6650285.613525] CS: 0010 DS: ES: CR0: 80050033 [6650285.620184] CR2: 01a78608 CR3: 003c28958000 CR4: 001427e0 [6650285.628426] Stack: [6650285.630895] 881fff803500 811c5b6e 883f3a2178c0 8830372a7f60 [6650285.639493] 8830372a7f58 8830372a7ed0 [6650285.648086] 811c5b6e 88228205f6c0 8830372a7f10 811c6086 [6650285.656704] Call Trace: [6650285.659678] [] ? alloc_pipe_info+0x3e/0xb0 [6650285.666342] [] alloc_pipe_info+0x3e/0xb0 [6650285.672811] [] create_pipe_files+0x46/0x200 [6650285.679574] [] ? vtime_account_user+0x54/0x60 [6650285.686529] [] __do_pipe_flags+0x34/0xf0 [6650285.692996] [] SyS_pipe+0x20/0xa0 [6650285.698791] [] tracesys+0xe1/0xe6 [6650285.704581] Code: dc 00 00 49 8b 50 08 4d 8b 20 49 8b 40 10 4d 85 e4 0f 84 14 01 00 00 48 85 c0 0f 84 0b 01 00 00 49 63 47 20 48 8d 4a 01 4d 8b 07 <49> 8b 1c 04 4c 89 e0 65 49 0f c7 08 0f 94 c0 84 c0 74 b9 49 63 [6650285.727070] RIP [] kmem_cache_alloc_trace+0x80/0x1f0 [6650285.734726] RSP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I did it, aand nothing works unfortunately :\ -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard
[Kernel-packages] [Bug 1887623] Re: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] Subsystem [1028:1810] not detected on Ubuntu 20.04
** Summary changed: - Atheros QCA9377 WiFi Not detected on Ubuntu 20.04 + Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] Subsystem [1028:1810] not detected on Ubuntu 20.04 ** Tags added: hww-networking-wifi -- 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/1887623 Title: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] Subsystem [1028:1810] not detected on Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: I am using Ubuntu 20.04 on Dell 5575 with AMD Ryzen 5. WiFi was working during installation and after the I updated recent, it stopped working. lspci | grep Atheros 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) dmesg errors [5.627332] ath10k_core_register_work+0x26/0x120 [ath10k_core] [5.627355] ath10k_pci :03:00.0: unable to get target info from device [5.627358] ath10k_pci :03:00.0: could not get target info (-5) [5.627373] ath10k_pci :03:00.0: could not probe fw (-5) have tried using older kernel 5.4.0-26 but that didn't help. I had to add this to grub, "nomodeset iommu=off" as it wasn't booting. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: poonam 1564 F pulseaudio /dev/snd/controlC0: poonam 1564 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-13 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=72998a7f-f0f6-4782-b447-785cc101a1ac ro quiet splash nomodeset iommu=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-40-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: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 0M0Y6P dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527062] Re: XFS Deadlock on 4.2+
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1527062 Title: XFS Deadlock on 4.2+ Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux-lts-utopic source package in Vivid: Invalid Status in linux source package in Wily: Fix Released Status in linux-lts-utopic source package in Wily: Invalid Bug description: [Impact] * An XFS Deadlock situation is possible on kernels older than 4.4rc1^ * Hung tasks have stack traces similar to [ 4559.110607] INFO: task kworker/1:0:17 blocked for more than 120 seconds. [ 4559.143010] Not tainted 4.2.0-18-generic #22~14.04.1-Ubuntu [ 4559.171972] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4559.209753] kworker/1:0 D 017 2 0x [ 4559.209791] Workqueue: xfs-cil/sdac1 xlog_cil_push_work [xfs] [ 4559.209794] 88085be9fbb8 0046 88085b746040 88085be8a940 [ 4559.209795] 88085bea 880107fddcc0 88085be8a940 [ 4559.209797] 880859119c00 880859119d00 88085be9fbd8 817b6a77 [ 4559.209798] Call Trace: [ 4559.209806] [] schedule+0x37/0x80 [ 4559.209817] [] xlog_state_get_iclog_space+0xdb/0x2d0 [xfs] [ 4559.209822] [] ? wake_up_q+0x80/0x80 [ 4559.209832] [] xlog_write+0x191/0x6a0 [xfs] [ 4559.209835] [] ? prandom_u32+0x18/0x20 [ 4559.209845] [] xlog_cil_push+0x1f9/0x3b0 [xfs] [ 4559.209854] [] xlog_cil_push_work+0x15/0x20 [xfs] [ 4559.209857] [] process_one_work+0x14e/0x3d0 [ 4559.209858] [] worker_thread+0x11a/0x470 [ 4559.209860] [] ? rescuer_thread+0x310/0x310 [ 4559.209862] [] kthread+0xd2/0xf0 [ 4559.209863] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 4559.209865] [] ret_from_fork+0x3f/0x70 [ 4559.209866] [] ? kthread_create_on_node+0x1c0/0x1c0 or [305651.804853] INFO: task kswapd0:194 blocked for more than 120 seconds. [305651.836092] Not tainted 4.2.0-18-generic #22~14.04.1-Ubuntu [305651.865655] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [305651.903596] kswapd0 D 88085fa96640 0 194 2 0x [305651.903614] 8810591ab858 0046 88085c2c2940 88105b19a940 [305651.903616] 880066c64548 8810591ac000 8808599cae18 [305651.903618] 88105b19a940 88085a2cb000 8810591ab878 817b6a77 [305651.903620] Call Trace: [305651.903629] [] schedule+0x37/0x80 [305651.903655] [] _xfs_log_force_lsn+0x15c/0x2d0 [xfs] [305651.903662] [] ? wake_up_q+0x80/0x80 [305651.903675] [] xfs_log_force_lsn+0x2e/0x80 [xfs] [305651.903687] [] ? xfs_iunpin_wait+0x19/0x20 [xfs] [305651.903698] [] __xfs_iunpin_wait+0x8d/0x120 [xfs] [305651.903701] [] ? autoremove_wake_function+0x40/0x40 [305651.903711] [] xfs_iunpin_wait+0x19/0x20 [xfs] [305651.903721] [] xfs_reclaim_inode+0x125/0x330 [xfs] [305651.903732] [] xfs_reclaim_inodes_ag+0x248/0x360 [xfs] [305651.903735] [] ? destroy_inode+0x3c/0x60 [305651.903744] [] xfs_reclaim_inodes_nr+0x33/0x40 [xfs] [305651.903755] [] xfs_fs_free_cached_objects+0x19/0x20 [xfs] [305651.903758] [] super_cache_scan+0x181/0x190 [305651.903761] [] shrink_slab+0x206/0x380 [305651.903763] [] shrink_zone+0x291/0x2b0 [305651.903764] [] kswapd+0x500/0x9b0 [305651.903766] [] ? mem_cgroup_shrink_node_zone+0x130/0x130 [305651.903768] [] kthread+0xd2/0xf0 [305651.903770] [] ? kthread_create_on_node+0x1c0/0x1c0 [305651.903772] [] ret_from_fork+0x3f/0x70 [305651.903774] [] ? kthread_create_on_node+0x1c0/0x1c0 [Test Case] * Large numbers of IO tasks to large numbers of XFS fileystems while under memory pressure. Testcase may not be guaranteed. [Regression Potential] * Upstream commit https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7a29ac474a47eb8cf212b45917683ae89d6fa13b - This commit allocates rescuer threads for each of the XFS work queues. * Possible additional memory usage from rescuer threads. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1469482] Re: Installer initrd missing kernel module for ib_ipoib network installation
Thanks for the report! Since Trusty is no longer supported, except for security fixes, I'll mark this LP as Won't Fix - if it reproduces in newer Ubuntu releases, please let us know. By the way, maybe using kernel 4.4 (HWE) has a fix for this even in Trusty. Cheers, Guilherme ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: linux-lts-vivid (Ubuntu) Status: New => Won't Fix ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1469482 Title: Installer initrd missing kernel module for ib_ipoib network installation Status in linux package in Ubuntu: Won't Fix Status in linux-lts-vivid package in Ubuntu: Won't Fix Status in linux source package in Trusty: Won't Fix Status in linux-lts-vivid source package in Trusty: Won't Fix Bug description: The initrd.gz found at the path [1] on Ubuntu 14.04.3 iso from [2] URL doesn't contain [3] kernel modules. This modules needed for network installation over ib_ipoib. To check if the modules aren't exist run: # lsinitrd install/netboot/ubuntu-installer/amd64/initrd.gz | grep infiniband [1] - install/netboot/ubuntu-installer/amd64/initrd.gz [2] - http://cdimage.ubuntu.com/ubuntu-server/trusty/daily/current/ [3] - ib_addr, ib_core, ib_cm, ib_sa, mlx4_core, mlx4_ib, mlx5_core, mlx5_ib, ib_mad, ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1469482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456952] Re: support the slub_debug boot option on specific object size
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1456952 Title: support the slub_debug boot option on specific object size Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux source package in Vivid: Fix Released Bug description: [Impact] slub_debug cannot work for specific kmem_cache size. e. g. slub_debug=PU,kmalloc-1024 The slub_debug is used to enable the debugging of use-after-free, poison overwritten, double free. And it also increases the up time of the server when the above mentioned errors happen instead of crashing immediately. However, currently, there exists bug that the slub_debug cannot be applied for the specific object size. This is not helpful to enable the whole system slub_debug because the performance loss will be up to 20%~30% according to the customer's measurement. The patch here to limit the slub_debug only on the specific object size to alleviate the performance loss. [Fix] The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s->name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s->flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. [Test case] Install the patched kernel. sudo reboot sudo vim /etc/default/grub append "slub_debug=FPZU,kmalloc-1024" to GRUB_CMDLINE_LINUX_DEFAULT sudo update-grub sudo reboot # Check if the kmalloc-1024 debug options are enabled sudo cat /sys/kernel/slab/kmalloc-1024/sanity_checks # shoulb be 1 sudo cat /sys/kernel/slab/kmalloc-1024/red_zone # shoulb be 1 sudo cat /sys/kernel/slab/kmalloc-1024/poison # shoulb be 1 # Check other object size sudo cat /sys/kernel/slab/kmalloc-8/sanity_checks # shoulb be 0 sudo cat /sys/kernel/slab/kmalloc-8/red_zone # shoulb be 0 sudo cat /sys/kernel/slab/kmalloc-8/poison # shoulb be 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
This problem just appeared on my Spectre x360 for the first time yesterday. When laptop auto-suspends form lack of activity, the screen goes black with three messages with this error. It is unresponsive so only solution is power off and reboot by pressing and holding the power button to shut down, then pressing again to power up. I was unaware of the keyboard factor so I will try to see if I can access via ssh and see if computer is still running. -- 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/1807406 Title: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, Message after returning from suspension dmesg: [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response from ISHTP device Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 12:02:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887703] [NEW] 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller
Public bug reported: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Tags: blocks-hwcert-server ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Tags added: blocks-hwcert-server -- 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/1887703 Title: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active
Re: [Kernel-packages] [Bug 1887340] Re: system freezes including keyboard and mouse whenever a CD is played
Okay. Will try that. On Wed, 15 Jul 2020, 12:05 pm Kai-Heng Feng, <1887...@bugs.launchpad.net> wrote: > Would it be possible for you to do a kernel bisection? > > First, find the last -rc kernel works and the first -rc kernel doesn’t > work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ > > Then, > $ sudo apt build-dep linux > $ git clone git:// > git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > $ cd linux > $ git bisect start > $ git bisect good $(the working version you found) > $ git bisect bad $(the non-working version found) > $ make localmodconfig > $ make -j`nproc` deb-pkg > Install the newly built kernel, then reboot with it. > If it still have the same issue, > $ git bisect bad > Otherwise, > $ git bisect good > Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1887340 > > Title: > system freezes including keyboard and mouse whenever a CD is played > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887340 Title: system freezes including keyboard and mouse whenever a CD is played Status in linux package in Ubuntu: Incomplete Bug description: Consistently, whenever a CD is played, the system freezes including keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pks1207 F pulseaudio /dev/snd/controlC2: pks1207 F pulseaudio /dev/snd/controlC0: pks1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 11:42:33 2020 InstallationDate: Installed on 2020-01-06 (188 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=ff43ab9d-9612-4215-8f0c-d11964542c44 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-16 (57 days ago) dmi.bios.date: 05/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A88-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887703] 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 1887703 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 ** Changed in: linux (Ubuntu Focal) 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/1887703 Title: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887461] Re: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04
Hi! 430.64-0ubuntu0~gpu14.04.3 works and I don't see any issues. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1887461 Title: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04 Status in nvidia-graphics-drivers-384 package in Ubuntu: Fix Released Bug description: when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430 package had the version 64 update that was just released a few days ago. After installing it, my system wouldn't boot to xwindows. Failsafe boot to gui wouldn't work either The error messages looked similar to this bug report for nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 Here's what my xorg.[0,failsafe].log showed: [43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 18:41:16 2020 [43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe" [43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [43.645] Parse error on line 7 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf "OutputClass" is not a valid section name. [43.645] (EE) Problem parsing the config file [43.645] (EE) Error parsing the config file [43.645] (EE) Fatal server error: [43.645] (EE) no screens found(EE) I have a *directory* named what the file is looking for (at least now after I downgraded nvidia...) here is the contents: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat nvidia-drm-outputclass.conf # This xorg.conf.d configuration snippet configures the X server to # automatically load the nvidia X driver when it detects a device driven by the # nvidia-drm.ko kernel module. Please note that this only works on Linux kernels # version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko # kernel module is loaded before the X server is started. Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" EndSection basically, in the progress of filing this bug report, I downgraded to nvidia-418 and my system was about to boot again. To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1887461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875150] Re: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged
Facing this issue as well with 5.7.7 on 20.04. Tried to use logiops and libratbag to configure the mouse better (MX Master 3). Right now I have two unified receiver dongles connects because I have not taken the time to pair all devices to a single receiver. Would love pointers on how to fix this. -- 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/1875150 Title: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged Status in linux package in Ubuntu: Incomplete Bug description: The mouse is MX Anywhere 2, the keyboard is K750. If the system is booted with the Logitech Unifying Receiver plugged in, the keyboard and mouse will keep losing connection. This is most visible after a short inactivity, i.e. I start typing and nothing appears on screen for a couple of seconds, or I start moving the mouse and the cursor takes a couple of seconds to start moving. This also happens while I'm using the input device, as I was typing this paragraph the keyboard cut out twice for a second or two. Additionally, every second time the mouse reconnects, scrolling via the scroll wheel is painfully slow. When this is going on, dmesg gets once in some seconds: [ 381.185787] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 507.351776] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 540.005778] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 627.051731] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 769.329768] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 I guess it happens when the mouse reconnects. This can be fixed by unplugging and replugging the Unifying Receiver. This fixes the problem until next boot. I tried a couple of older kernel versions and the same thing happened. I also just tried Fedora 32 beta and it didn't happen there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: domin 2235 F pulseaudio /dev/snd/controlC0: domin 2235 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Apr 26 10:25:57 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-12 (926 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=a2abd949-9a7b-43a5-9453-7471311a309b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-26 (30 days ago) WifiSyslog: dmi.bios.date: 08/07/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP61.88Z.005A.B00.1708072217 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.005A.B00.1708072217:bd08/07/17:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887564] Re: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached.
If this problem only occurs after you upgrade kernel, we may be able to identify the regression patch by bisecting kernels if a passing kernel version is shared. -- 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/1887564 Title: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached. Status in linux package in Ubuntu: Incomplete Bug description: (Ubuntu 4.4.0-185.215-generic 4.4.224) If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13 10:24:24 xps kernel: [318785.375145] PM: Syncing filesystems ... done. Jul 13 10:24:24 xps kernel: [318785.424201] PM: Preparing system for sleep (freeze) Jul 13 10:24:24 xps kernel: [318785.424337] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 13 10:24:24 xps kernel: [318785.426132] Freezing remaining freezable tasks ... (elapsed 0.037 seconds) done. Jul 13 10:24:24 xps kernel: [318785.463699] PM: Suspending system (freeze) Jul 13 10:24:24 xps kernel: [318785.463701] Suspending console(s) (use no_console_suspend to debug) Jul 13 10:24:24 xps kernel: [318785.463921] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 13 10:24:24 xps kernel: [318785.463971] sd 0:0:0:0: [sda] Stopping disk Jul 13 10:24:24 xps kernel: [318786.150701] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Jul 13 10:24:24 xps kernel: [318786.150716] PM: Device usb4 failed to suspend async: error -16 Jul 13 10:24:24 xps kernel: [318786.150831] PM: Some devices failed to suspend, or early wake event detected Jul 13 10:24:24 xps kernel: [318786.166836] sd 0:0:0:0: [sda] Starting disk Jul 13 10:24:24 xps kernel: [318786.254775] rtc_cmos 00:01: System wakeup disabled by ACPI Jul 13 10:24:24 xps kernel: [318786.490641] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 13 10:24:24 xps kernel: [318786.513275] ata1.00: configured for UDMA/133 Jul 13 10:24:24 xps kernel: [318786.942366] PM: resume of devices complete after 791.556 msecs Jul 13 10:24:24 xps kernel: [318786.942703] PM: Finishing wakeup. Jul 13 10:24:24 xps kernel: [318786.942706] Restarting tasks ... done. Jul 13 10:24:24 xps systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Jul 13 10:24:24 xps kernel: [318786.967694] video LNXVIDEO:00: Restoring backlight state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
Following up, I have made the following changes to my system recently. Two occurred within the week prior to this problem appearing, but not immediately before to my knowledge, so it's not certain that any of them are applicable. They are listed in order of first use. - Added a 4K monitor on HDMI a month ago). - Switched from Intel graphics to NVidia. - Added a bluetooth speaker system, which took a bit of messing about with the GUI bluetooth devices panel before it finally decided to work. - Began using a bluetooth headset with my phone but not the laptop. Operating system is Mate 18.04. Kernel is 4.17.11-041711-generic Message in kern.log is as follows. When the failure happens there are three lines of text on the screen. The third line is different but I don't recall what it was, and it is not shown in kern.log. Jul 14 17:34:56 Hebegb kernel: [ 6618.034362] hid-sensor-hub 001F:8086:22D8.0005: timeout waiting for response from ISHTP device Jul 14 17:34:56 Hebegb kernel: [ 6618.034391] hid-sensor-hub 001F:8086:22D8.0004: timeout waiting for response from ISHTP device -- 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/1807406 Title: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, Message after returning from suspension dmesg: [13383.967611] hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device [13383.967615] hid-sensor-hub 001F:8086:22D8.0002: timeout waiting for response from ISHTP device Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.19.0-8-generic 4.19.0-8.9 ProcVersionSignature: Ubuntu 4.19.0-8.9-generic 4.19.6 Uname: Linux 4.19.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2769 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 12:02:26 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.19.0-8-generic N/A linux-backports-modules-4.19.0-8-generic N/A linux-firmware1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (4 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1807406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887716] [NEW] 10G-BaseT fails to Canonical Certification pxe boot
Public bug reported: 10G-BaseT unable to run pxe boot. use 10G-SFP able to pxe boot and deployed successful. Even logged, ip addr only show interface 10G-SFP x 2, 10G-BaseT are not present. Attached sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz" https://bugs.launchpad.net/bugs/1887716/+attachment/5392966/+files/sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz -- 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/1887716 Title: 10G-BaseT fails to Canonical Certification pxe boot Status in linux package in Ubuntu: New Bug description: 10G-BaseT unable to run pxe boot. use 10G-SFP able to pxe boot and deployed successful. Even logged, ip addr only show interface 10G-SFP x 2, 10G-BaseT are not present. Attached sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887715] [NEW] Bionic update: upstream stable patchset 2020-07-15
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-07-15 Ported from the following upstream stable releases: v4.14.187, v4.19.131 from git://git.kernel.org/ net: be more gentle about silly gso requests coming from user block/bio-integrity: don't free 'buf' if bio_integrity_add_page() failed net: sched: export __netdev_watchdog_up() fix a braino in "sparc32: fix register window handling in genregs32_[gs]et()" apparmor: don't try to replace stale label in ptraceme check ibmveth: Fix max MTU limit mld: fix memory leak in ipv6_mc_destroy_dev() net: bridge: enfore alignment for ethernet address net: fix memleak in register_netdevice() net: usb: ax88179_178a: fix packet alignment padding rocker: fix incorrect error handling in dma_rings_init rxrpc: Fix notification call on completion of discarded calls sctp: Don't advertise IPv4 addresses if ipv6only is set on the socket tcp: grow window for OOO packets only for SACK flows tg3: driver sleeps indefinitely when EEH errors exceed eeh_max_freezes ip_tunnel: fix use-after-free in ip_tunnel_lookup() tcp_cubic: fix spurious HYSTART_DELAY exit upon drop in min RTT ip6_gre: fix use-after-free in ip6gre_tunnel_lookup() net: Fix the arp error in some cases net: Do not clear the sock TX queue in sk_set_socket() net: core: reduce recursion limit value USB: ohci-sm501: Add missed iounmap() in remove usb: dwc2: Postponed gadget registration to the udc class driver usb: add USB_QUIRK_DELAY_INIT for Logitech C922 USB: ehci: reopen solution for Synopsys HC bug usb: host: xhci-mtk: avoid runtime suspend when removing hcd usb: host: ehci-exynos: Fix error check in exynos_ehci_probe() ALSA: usb-audio: add quirk for Denon DCD-1500RE xhci: Fix incorrect EP_STATE_MASK xhci: Fix enumeration issue when setting max packet size for FS devices. cdc-acm: Add DISABLE_ECHO quirk for Microchip/SMSC chip loop: replace kill_bdev with invalidate_bdev ALSA: usb-audio: Clean up mixer element list traverse ALSA: usb-audio: Fix OOB access of mixer element list xhci: Poll for U0 after disabling USB2 LPM cifs/smb3: Fix data inconsistent when punch hole cifs/smb3: Fix data inconsistent when zero file range efi/esrt: Fix reference count leak in esre_create_sysfs_entry. ARM: dts: NSP: Correct FA2 mailbox node rxrpc: Fix handling of rwind from an ACK packet RDMA/cma: Protect bind_list and listen_list while finding matching cm id ASoC: rockchip: Fix a reference count leak. RDMA/mad: Fix possible memory leak in ib_mad_post_receive_mads() net: qed: fix left elements count calculation net: qed: fix NVMe login fails over VFs net: qed: fix excessive QM ILT lines consumption ARM: imx5: add missing put_device() call in imx_suspend_alloc_ocram() usb: gadget: udc: Potential Oops in error handling code netfilter: ipset: fix unaligned atomic access net: bcmgenet: use hardware padding of runt frames sched/core: Fix PI boosting between RT and DEADLINE tasks ata/libata: Fix usage of page address by page_address in ata_scsi_mode_select_xlat function net: alx: fix race condition in alx_remove s390/ptrace: fix setting syscall number kbuild: improve cc-option to clean up all temporary files blktrace: break out of blktrace setup on concurrent calls ALSA: hda: Add NVIDIA codec IDs 9a & 9d through a0 to patch table ACPI: sysfs: Fix pm_profile_attr type KVM: X86: Fix MSR range of APIC registers in X2APIC mode KVM: nVMX: Plumb L2 GPA through to PML emulation btrfs: fix failure of RWF_NOWAIT write into prealloc extent beyond eof mm/slab: use memzero_explicit() in kzfree() ocfs2: load global_inode_alloc ocfs2: fix value of OCFS2_INVALID_SLOT ocfs2: fix panic on nfs server over ocfs2 arm64: perf: Report the PC value in REGS_ABI_32 mode tracing: Fix event trigger to accept redundant spaces drm/radeon: fix fb_div check in ni_init_smc_spll_table() Staging: rtl8723bs: prevent buffer overflow in update_sta_support_rate() sunrpc: fixed rollback in rpc_gssd_dummy_populate() SUNRPC: Properly set the @subbuf parameter of xdr_buf_subsegment() pNFS/flexfiles: Fix list corruption if the mirror count changes NFSv4 fix CLOSE not waiting for direct IO compeletion xfs: add agf freeblocks verify in xfs_agf_verify net: bcmgenet: remove HFB_CTRL access EDAC/amd64: Add Family 17h Model 30h PCI IDs i2c: tegra: Cleanup kerneldoc comments i2c: tegra: Add missing kerneldoc for some fields net: phy: Check harder for errors in get_phy_id() ALSA: usb-audio: add quirk for Samsung USBC Headset (AKG) scsi: zfcp: Fix panic on ERP timeout for previously dismissed ERP a
[Kernel-packages] [Bug 1807406] Re: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
Sorry, more info... looking at kern.log, the context is as follows. Note that this occurred when the machine had auto-suspended with the laptop open, and the black screen with text was already visible when I came into the room. It did not suddenly appear as a result of my triggering a return from suspend. At the end you can see the beginning of the power off process I started by pressing the power button. Jul 14 22:58:14 Hebegb kernel: [ 6874.519984] CPU2: Core temperature above threshold, cpu clock throttled (total events = 1621) Jul 14 22:58:14 Hebegb kernel: [ 6874.519985] CPU6: Core temperature above threshold, cpu clock throttled (total events = 1621) Jul 14 22:58:14 Hebegb kernel: [ 6874.519987] CPU6: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.519988] CPU2: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520032] CPU5: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520033] CPU0: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520034] CPU1: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520035] CPU4: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520036] CPU3: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520036] CPU7: Package temperature above threshold, cpu clock throttled (total events = 4509) Jul 14 22:58:14 Hebegb kernel: [ 6874.520983] CPU2: Core temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.520983] CPU6: Core temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.520984] CPU6: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.520985] CPU2: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.521029] CPU0: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.521030] CPU5: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.521030] CPU1: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.521031] CPU4: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.521032] CPU3: Package temperature/speed normal Jul 14 22:58:14 Hebegb kernel: [ 6874.521032] CPU7: Package temperature/speed normal Jul 14 22:58:25 Hebegb kernel: [ 6885.747439] wlo1: deauthenticating from 7a:ad:ec:af:0c:36 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 14 22:58:25 Hebegb kernel: [ 6886.034734] PM: suspend entry (deep) Jul 14 22:58:25 Hebegb kernel: [ 6886.034735] PM: Syncing filesystems ... done. Jul 14 23:00:16 Hebegb kernel: [ 6886.915305] Freezing user space processes ... (elapsed 0.002 seconds) done. Jul 14 23:00:16 Hebegb kernel: [ 6886.917622] OOM killer disabled. Jul 14 23:00:16 Hebegb kernel: [ 6886.917622] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 14 23:00:16 Hebegb kernel: [ 6886.918949] Suspending console(s) (use no_console_suspend to debug) Jul 14 23:00:16 Hebegb kernel: [ 6887.403105] ACPI: EC: interrupt blocked Jul 14 23:00:16 Hebegb kernel: [ 6887.458786] ACPI: Preparing to enter system sleep state S3 Jul 14 23:00:16 Hebegb kernel: [ 6887.472912] ACPI: EC: event blocked Jul 14 23:00:16 Hebegb kernel: [ 6887.472914] ACPI: EC: EC stopped Jul 14 23:00:16 Hebegb kernel: [ 6887.472915] PM: Saving platform NVS memory Jul 14 23:00:16 Hebegb kernel: [ 6887.472998] Disabling non-boot CPUs ... Jul 14 23:00:16 Hebegb kernel: [ 6887.487497] smpboot: CPU 1 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.511483] smpboot: CPU 2 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.539439] smpboot: CPU 3 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.556517] smpboot: CPU 4 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.578240] IRQ 123: no longer affine to CPU5 Jul 14 23:00:16 Hebegb kernel: [ 6887.579269] smpboot: CPU 5 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.603248] smpboot: CPU 6 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.626205] IRQ 132: no longer affine to CPU7 Jul 14 23:00:16 Hebegb kernel: [ 6887.626214] IRQ 133: no longer affine to CPU7 Jul 14 23:00:16 Hebegb kernel: [ 6887.626227] IRQ 148: no longer affine to CPU7 Jul 14 23:00:16 Hebegb kernel: [ 6887.627246] smpboot: CPU 7 is now offline Jul 14 23:00:16 Hebegb kernel: [ 6887.631198] ACPI: Low-level resume complete Jul 14 23:00:16 Hebegb kernel: [ 6887.631276] ACPI: EC: EC started Jul 14 23:00:16 Hebegb kernel: [ 6887.631277] PM: Restoring platform NVS memory Jul 14 23:00:16 Hebegb kernel: [ 6887.633788] Enabling non-boot CPUs ... Jul 14 23:00:16 Hebegb kernel: [ 6887.633826] x86: Booting SMP configuration: Jul 14 23:00:16 Hebegb kernel: [ 6887.633827] smpboot
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same error with me. Lenovo Thinkpad Yoga X380 with Ubuntu 20.04. I installed ubuntu on today's date and realized this flaw. -- 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/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887716] 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 1887716 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/1887716 Title: 10G-BaseT fails to Canonical Certification pxe boot Status in linux package in Ubuntu: Incomplete Bug description: 10G-BaseT unable to run pxe boot. use 10G-SFP able to pxe boot and deployed successful. Even logged, ip addr only show interface 10G-SFP x 2, 10G-BaseT are not present. Attached sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Same problem here with a Dell XPS 15 2 in 1 9575. BIOS version 1.11. Problem fixed with blacklisting intel_vbtn in /etc/modprobe.d/ -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779872] Re: snapd.seeded.service taking over 2 minutes to initialise (kernel crng regression?)
** Changed in: snapd Status: Confirmed => Fix Released ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => 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/1779872 Title: snapd.seeded.service taking over 2 minutes to initialise (kernel crng regression?) Status in snapd: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Following a regular dist-upgrade on Ubuntu 18.04 this morning, reboot and further reboots were hanging for minutes rather than seconds on the Ubuntu splash screen before getting to login. Initial system analysis: $ sudo systemd-analyze blame 3min 53.073s plymouth-quit-wait.service 2min 20.699s snapd.seeded.service 49.949s snapd.service 6.186s NetworkManager-wait-online.service 1.148s dev-sda2.device 1.098s plymouth-start.service Drill down on snapd.seeded.service $ journalctl -u snapd.seeded.service --since today -- Logs begin at Fri 2018-04-27 13:01:30 BST, end at Tue 2018-07-03 12:42:14 BST. -- (BEFORE UPGRADE) Jul 03 04:15:43 user-laptop systemd[1]: Starting Wait until snapd is fully seeded... Jul 03 04:15:43 user-laptop systemd[1]: Started Wait until snapd is fully seeded. Jul 03 04:21:03 user-laptop systemd[1]: Stopped Wait until snapd is fully seeded. (/BEFORE UPGRADE) -- Reboot -- (AFTER UPGRADE) Jul 03 04:22:47 user-laptop systemd[1]: Starting Wait until snapd is fully seeded... Jul 03 04:24:49 user-laptop systemd[1]: Started Wait until snapd is fully seeded. Jul 03 04:26:23 user-laptop systemd[1]: Stopped Wait until snapd is fully seeded. -- Reboot -- Jul 03 04:28:17 user-laptop systemd[1]: Starting Wait until snapd is fully seeded... Jul 03 04:30:44 user-laptop systemd[1]: Started Wait until snapd is fully seeded. Jul 03 10:23:14 user-laptop systemd[1]: Stopped Wait until snapd is fully seeded. -- Reboot -- Jul 03 10:29:30 user-laptop systemd[1]: Starting Wait until snapd is fully seeded... Jul 03 10:31:50 user-laptop systemd[1]: Started Wait until snapd is fully seeded. (/AFTER UPGRADE) I reported this issue on AskUbuntu, and it was suggested to me to report a possible snapd bug due to the extended seeding time compared to before the upgrade. The dist-upgrade installed/upgraded: Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic) Upgrade: gnome-control-center-data:amd64 (1:3.28.1-0ubuntu1.18.04.1, 1:3.28.1-0ubuntu1.18.04.2), linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), gnome-control-center:amd64 (1:3.28.1-0ubuntu1.18.04.1, 1:3.28.1-0ubuntu1.18.04.2), linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-signed-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), gnome-control-center-faces:amd64 (1:3.28.1-0ubuntu1.18.04.1, 1:3.28.1-0ubuntu1.18.04.2), linux-generic:amd64 (4.15.0.23.25, 4.15.0.24.26) UPDATE (2018-07-05) This morning's Boot: $ sudo systemd-analyze blame 14.161s apt-daily.service 6.177s NetworkManager-wait-online.service 3.452s plymouth-quit-wait.service 1.252s dev-sda2.device 1.091s plymouth-start.service . . . 24ms snapd.seeded.service To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1779872/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775326] Re: The kernel NULL pointer dereference happens when accessing the task_struct by task_cpu() in function cpuacct_charge()
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1775326
Title:
The kernel NULL pointer dereference happens when accessing the
task_struct by task_cpu() in function cpuacct_charge()
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
In function cpuacct_charge(), the NULL pointer dereference happens
with the stack pointer being zero inside the task_struct when the
task_cpu() is trying to access the member CPU of the struct
thread_info inside the stack. It's a use-after-free corruption
happening in the situation that the task_struct is released almost
concurrently before accessing the task_struct->stack.
void cpuacct_charge(struct task_struct *tsk, u64 cputime)
{
struct cpuacct *ca;
int cpu;
cpu = task_cpu(tsk);
rcu_read_lock();
ca = task_ca(tsk);
while (true) {
u64 *cpuusage = per_cpu_ptr(ca->cpuusage, cpu);
*cpuusage += cputime;
ca = parent_ca(ca);
if (!ca)
break;
}
rcu_read_unlock();
}
BUG: unable to handle kernel NULL pointer dereference at 0010
IP: [] cpuacct_charge+0x14/0x40
PGD 0
Oops: [#1] SMP
CPU: 10 PID: 148614 Comm: qemu-system-x86 Tainted: PW OE
4.4.0-45-generic #66~14.04.1-Ubuntu
Hardware name: Dell Inc. PowerEdge R630/02C2CP, BIOS 2.1.7 06/16/2016
task: 881ff0f01b80 ti: 88018fd7 task.ti: 88018fd7
RIP: 0010:[] [] cpuacct_charge+0x14/0x40
RSP: 0018:88018fd73d10 EFLAGS: 00010246
RAX: RBX: 8801931e8000 RCX: 88010caff200
RDX: 880124508000 RSI: 0066f757398831d6 RDI: 8801931e7fa0
RBP: 88018fd73d10 R08: c04b8320 R09: 0001
R10: 0001 R11: R12: 0066f757398831d6
R13: 0066f757398b8997 R14: 8801931e7fa0 R15: 0001
FS: 7f162aaf7700() GS:881ffe74() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 0010 CR3: 00011d86e000 CR4: 003426e0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Stack:
88018fd73d28 810b1a9f 8801931e8000 88018fd73d40
c069df72 8801931e8000 88018fd73da8 c069f121
881ff0f01b80 881ff0f01b80 810bddc0
Call Trace:
[] update_curr+0xdf/0x170
[] kvm_vcpu_check_block+0x12/0x60 [kvm]
[] kvm_vcpu_block+0x191/0x2d0 [kvm]
[] ? prepare_to_wait_event+0xf0/0xf0
[] kvm_arch_vcpu_ioctl_run+0x17e/0x3d0 [kvm]
[] kvm_vcpu_ioctl+0x2ab/0x640 [kvm]
[] ? perf_event_context_sched_in+0x87/0xa0
[] do_vfs_ioctl+0x2dd/0x4c0
[] ? __audit_syscall_entry+0xaf/0x100
[] ? do_audit_syscall_entry+0x66/0x70
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x75
Code: 9a 11 00 5b 48 c7 c0 f4 ff ff ff 5d eb df 66 0f 1f 84 00 00 00 00 00 0f
1f 44 00 00 55 48 8b 47 08 48 8b 97 78 07 00 00 48 89 e5 <48> 63 48 10 48 8b 52
60 48 8b 82 b8 00 00 00 48 03 04 cd c0 7a
RIP [] cpuacct_charge+0x14/0x40
RSP
CR2: 0010
---[ end trace 419a30375d0e4622 ]---
[Fix]
The patch uses this_cpu_ptr() instead of getting the CPU number by
task_cpu() and proceeds to get the cpu_usage by per_cpu_ptr(). And
that can avoid accessing the thread_info inside the stack.
commit 73e6aafd9ea81498d31361f01db84a0118da2d1c
Author: Zhao Lei
Date: Thu Mar 17 12:19:43 2016 +0800
sched/cpuacct: Simplify the cpuacct code
- Use for() instead of while() loop in some functions
to make the code simpler.
- Use this_cpu_ptr() instead of per_cpu_ptr() to make the code
cleaner and a bit faster.
Suggested-by: Peter Zijlstra
Signed-off-by: Zhao Lei
Signed-off-by: Peter Zijlstra (Intel)
Cc: Linus Torvalds
Cc: Tejun Heo
Cc: Thomas Gleixner
Link:
http://lkml.kernel.org/r/d8a7ef9592f55224630cb26dea239f05b6398a4e.1458187654.git.zhao...@cn.fujitsu.com
Signed-off-by: Ingo Molnar
[Test]
The test kernel has been tested by the Qemu and cannot be reproduced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775326/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840043] Re: bcache: Performance degradation when querying priority_stats
** Changed in: linux
Status: Fix Committed => 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/1840043
Title:
bcache: Performance degradation when querying priority_stats
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
Querying bcache's priority_stats attribute in sysfs causes severe performance
degradation for read/write workloads and occasional system stalls
[Test Case]
Note: As the sorting step has the most noticeable performance impact, the
test case below pins a workload and the sysfs query to the same CPU. CPU
contention issues still occur without any pinning, this just removes the
scheduling factor of landing in different CPUs and affecting different tasks.
1) Start a read/write workload on the bcache device with e.g. fio or dd,
pinned to a certain CPU:
# taskset 0x10 dd if=/dev/zero of=/dev/bcache0 bs=4k status=progress
2) Start a sysfs query loop for the priority_stats attribute pinned to the
same CPU:
# for i in {1..10}; do taskset 0x10 cat
/sys/fs/bcache/*/cache0/priority_stats > /dev/null; done
3) Monitor the read/write workload for any performance impact
[Fix]
To fix CPU contention and performance impact, a cond_resched() call is
introduced in the priority_stats sort comparison.
[Regression Potential]
Regression potential is low, as the change is confined to the priority_stats
sysfs query. In cases where frequent queries to bcache priority_stats take
place (e.g. node_exporter), the impact should be more noticeable as those could
now take a bit longer to complete. A regression due to this patch would most
likely show up as a performance degradation in bcache-focused workloads.
--
[Description]
In the latest bcache drivers, there's a sysfs attribute that calculates
bucket priority statistics in /sys/fs/bcache/*/cache0/priority_stats. Querying
this file has a big performance impact on tasks that run in the same CPU, and
also affects read/write performance of the bcache device itself.
This is due to the way the driver calculates the stats: the bcache
buckets are locked and iterated through, collecting information about
each individual bucket. An array of nbucket elements is constructed
and sorted afterwards, which can cause very high CPU contention in
cases of larger bcache setups.
From our tests, the sorting step of the priority_stats query causes
the most expressive performance reduction, as it can hinder tasks that
are not even doing any bcache IO. If a task is "unlucky" to be
scheduled in the same CPU as the sysfs query, its performance will be
harshly reduced as both compete for CPU time. We've had users report
systems stalls of up to ~6s due to this, as a result from monitoring
tools that query the priority_stats periodically (e.g. Prometheus Node
Exporter from [0]). These system stalls have triggered several other
issues such as ceph-mon re-elections, problems in percona-cluster and
general network stalls, so the impact is not isolated to bcache IO
workloads.
An example benchmark can be seen in [1], where the read performance on
a bcache device suffered quite heavily (going from ~40k IOPS to ~4k
IOPS due to priority_stats). Other comparison charts are found under
[2].
[0] https://github.com/prometheus/node_exporter
[1]
https://people.canonical.com/~halves/priority_stats/read/4k-iops-2Dsmooth.png
[2] https://people.canonical.com/~halves/priority_stats/
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1840043/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848739] Re: [linux] Patch to prevent possible data corruption
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-azure (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1848739
Title:
[linux] Patch to prevent possible data corruption
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux-azure source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Invalid
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657281] Re: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue
** 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/1657281 Title: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] * When running block device I/O on an Amazon i3 system there is a performance degradation. A patch with git change id 87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel series increases I/O performance. * Fix should be backported to xenial 4.4 series to avoid more support issues being filed. * This change gets rid of uneccessary work being performed. [Test Case] * Steps to reproduce below 1) partition ephemeral disks /sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 0% 100% /sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 0% 100% /sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 0% 100% /sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 0% 100% 2) create raid array /sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 --raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 3) create pv /sbin/pvcreate --force --metadatasize 4092k /dev/md0 4) create volume group /sbin/vgcreate RDSVG /dev/md0 5) create lv /sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 5) test I/O sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync [Regression Potential] * No known regression potential. [Original Description] When we were doing testing on i3, we noticed that it is taking significantly longer to perform operations when using software RAID than without, we believe this is resolved in an upstream commit: http://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da So stock 4.4.0-59-generic performs ok: $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync sudo: unable to resolve host ip-10-0-85-167 100+0 records in 100+0 records out 819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s and the patch you originally providing works a little bit better (as expected): $ uname -a Linux ip-10-0-85-167 4.4.0-57-generic #78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync sudo: unable to resolve host ip-10-0-85-167 100+0 records in 100+0 records out 819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806682] Re: ACPI: Invalid passive threshold
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1806682 Title: ACPI: Invalid passive threshold Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [1.423794] ACPI: Invalid passive threshold Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio /dev/snd/pcmC0D0p: caravena 2739 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:17:14 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887716] Re: 10G-BaseT fails to Canonical Certification pxe boot
*** This bug is a duplicate of bug 1887703 *** https://bugs.launchpad.net/bugs/1887703 ** This bug has been marked a duplicate of bug 1887703 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller -- 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/1887716 Title: 10G-BaseT fails to Canonical Certification pxe boot Status in linux package in Ubuntu: Incomplete Bug description: 10G-BaseT unable to run pxe boot. use 10G-SFP able to pxe boot and deployed successful. Even logged, ip addr only show interface 10G-SFP x 2, 10G-BaseT are not present. Attached sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887703] Re: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller
Also, from syslog in the sosreport, looks like something bad happens when the driver loads and the first two ports are probed: Jul 15 15:18:05 usable-sloth kernel: [ 26.841704] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 2.8.20-k Jul 15 15:18:05 usable-sloth kernel: [ 26.844779] i40e: Copyright (c) 2013 - 2019 Intel Corporation. Jul 15 15:18:05 usable-sloth kernel: [ 26.928593] i40e :33:00.0: unidentified MAC or BLANK NVM: -11 Jul 15 15:18:05 usable-sloth kernel: [ 26.928704] i40e: probe of :33:00.0 failed with error -11 Jul 15 15:18:05 usable-sloth kernel: [ 26.950964] i40e :33:00.1: unidentified MAC or BLANK NVM: -11 Jul 15 15:18:05 usable-sloth kernel: [ 26.951057] i40e: probe of :33:00.1 failed with error -11 Jul 15 15:18:05 usable-sloth kernel: [ 26.973459] i40e :33:00.2: fw 7.2.60285 api 1.9 nvm 7.21 0x80007959 1.2585.0 [8086:104e] [15d9:] Jul 15 15:18:05 usable-sloth kernel: [ 27.297613] i40e :33:00.2: MAC address: 3c:ec:ef:3f:b2:16 Jul 15 15:18:05 usable-sloth kernel: [ 27.298878] i40e :33:00.2: FW LLDP is enabled Jul 15 15:18:05 usable-sloth kernel: [ 27.314610] i40e :33:00.2 eth0: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None Jul 15 15:18:05 usable-sloth kernel: [ 27.344689] i40e :33:00.2: PCI-Express: Speed 8.0GT/s Width x8 Jul 15 15:18:05 usable-sloth kernel: [ 27.353837] i40e :33:00.2: Features: PF-id[2] VFs: 32 VSIs: 34 QP: 119 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA Jul 15 15:18:05 usable-sloth kernel: [ 27.375077] i40e :33:00.3: fw 7.2.60285 api 1.9 nvm 7.21 0x80007959 1.2585.0 [8086:104e] [15d9:] Jul 15 15:18:05 usable-sloth kernel: [ 27.627129] i40e :33:00.3: MAC address: 3c:ec:ef:3f:b2:17 Jul 15 15:18:05 usable-sloth kernel: [ 27.627800] i40e :33:00.3: FW LLDP is enabled Jul 15 15:18:05 usable-sloth kernel: [ 27.628476] i40e :33:00.3: Query for DCB configuration failed, err I40E_ERR_NOT_READY aq_err OK Jul 15 15:18:05 usable-sloth kernel: [ 27.628955] i40e :33:00.3: DCB init failed -63, disabled Jul 15 15:18:05 usable-sloth kernel: [ 27.639670] i40e :33:00.3 eth1: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None Jul 15 15:18:05 usable-sloth kernel: [ 27.659332] i40e :33:00.3: PCI-Express: Speed 8.0GT/s Width x8 Jul 15 15:18:05 usable-sloth kernel: [ 27.670480] i40e :33:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 119 RSS FD_ATR FD_SB NTUPLE VxLAN Geneve PTP VEPA Jul 15 15:18:05 usable-sloth kernel: [ 27.672306] i40e :33:00.2 eno3: renamed from eth0 Jul 15 15:18:05 usable-sloth kernel: [ 27.702841] i40e :33:00.3 eno4: renamed from eth1 -- 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/1887703 Title: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation"
[Kernel-packages] [Bug 1887703] Re: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller
>From the duplicate bug is a sosreport from the failing system: ** Attachment added: "sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+attachment/5392990/+files/sosreport-usable-sloth-1-2020-07-15-telgxfb.tar.xz -- 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/1887703 Title: 5.4 is not identifying all ports on Intex x710-TM4 10GbE controller Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card: 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) 625: PCI 3300.2: 0200 Ethernet controller [Created at pci.386] Unique ID: rz7Q.2osif2+gzUA Parent ID: dkRe.4r+z9AQbRI0 SysFS ID: /devices/pci:32/:32:00.0/:33:00.2 SysFS BusID: :33:00.2 Hardware Class: network Device Name: "Intel Ethernet X710-TM4 #3" Model: "Intel Ethernet Controller X710 for 10 Gigabit SFP+" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x104e "Ethernet Controller X710 for 10 Gigabit SFP+" SubVendor: pci 0x15d9 "Super Micro Computer Inc" SubDevice: pci 0x Revision: 0x02 Driver: "i40e" Driver Modules: "i40e" Device File: eno3 Memory Range: 0xa700-0xa7ff (ro,non-prefetchable) Memory Range: 0xaa808000-0xaa80 (ro,non-prefetchable) Memory Range: 0xa450-0xa457 (ro,non-prefetchable,disabled) IRQ: 60 (no events) HW Address: 3c:ec:ef:3f:b2:16 Permanent HW Address: 3c:ec:ef:3f:b2:16 Link detected: yes Module Alias: "pci:v8086d104Esv15D9sdbc02sc00i00" Driver Info #0: Driver Status: i40e is active Driver Activation Cmd: "modprobe i40e" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #794 (PCI bridge) However, Ubuntu does not see the copper ports... it will only address/configure the two SFP+ ports. This is currently blocking certification for one of our hardware partners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-5.6 (Ubuntu) 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/1886247 Title: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: SRU justification: [Impact] New realtek wifi card ID found on ThinkCentre. No driver is loaded to support it. [Fix] This wifi card is very similar as 0xc822 in rtw88. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Add new ID to supported driver. Test on hw, double confirmed by LP bugs. This patch is backported from original link due to the 5.8-rc1 driver file path changed, no function changed. Maintainer had merged: https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351 This git repo is moving by maintainer, not availible by now. = 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f Looking for a working solution on a fresh install (USB BOOT) of Ubuntu. A work-around helped, for a while, but I would really like to disconnect my Wifi Dongel and use my brand new laptop! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1277 F pulseaudio /dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 07:58:06 2020 InstallationDate: Installed on 2020-06-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux StagingDrivers: r8712u UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) 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/1886247 Title: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: SRU justification: [Impact] New realtek wifi card ID found on ThinkCentre. No driver is loaded to support it. [Fix] This wifi card is very similar as 0xc822 in rtw88. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Add new ID to supported driver. Test on hw, double confirmed by LP bugs. This patch is backported from original link due to the 5.8-rc1 driver file path changed, no function changed. Maintainer had merged: https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351 This git repo is moving by maintainer, not availible by now. = 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f Looking for a working solution on a fresh install (USB BOOT) of Ubuntu. A work-around helped, for a while, but I would really like to disconnect my Wifi Dongel and use my brand new laptop! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1277 F pulseaudio /dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 07:58:06 2020 InstallationDate: Installed on 2020-06-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux StagingDrivers: r8712u UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887727] [NEW] Permission denied opening file in a directory with a sticky bit
Public bug reported: We just upgraded to Ubuntu 20.04, so we're now running version 0.8.3-1ubuntu12.1 of zfsutils-linux and related packages. We have a backup server that's essentially rsyncing files from remote systems. After the upgrade we started getting Permission denied failures on a few files, which match a specific pattern: In a directory with a sticky bit set: /zfs# mkdir testdir /zfs# chmod a+t testdir ... which is group writable: /zfs# chmod g+w testdir ... and has an existing file: /zfs# touch testdir/test ... which has a uid which isn't present on the system: /zfs# chown testdir/test ... then an open() call with O_CREAT fails with Permission denied: /zfs# ./openat testdir/test Error opening testdir/test: Permission denied (13) Skip any of those steps and it doesn't throw the error. It's just that specific configuration of directory permissions and file ownership that seems to do it. The ./openat is a simple test case that just runs open() (so named as I was originally testing with the openat() call) and it's attached for reference. We have an rsync --inplace that gets us into that specific scenario. Dropping the --inplace works around it, FWIW, but then we lose a little space within the ZFS snapshots. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Test case" https://bugs.launchpad.net/bugs/1887727/+attachment/5393017/+files/openat.c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1887727 Title: Permission denied opening file in a directory with a sticky bit Status in zfs-linux package in Ubuntu: New Bug description: We just upgraded to Ubuntu 20.04, so we're now running version 0.8.3-1ubuntu12.1 of zfsutils-linux and related packages. We have a backup server that's essentially rsyncing files from remote systems. After the upgrade we started getting Permission denied failures on a few files, which match a specific pattern: In a directory with a sticky bit set: /zfs# mkdir testdir /zfs# chmod a+t testdir ... which is group writable: /zfs# chmod g+w testdir ... and has an existing file: /zfs# touch testdir/test ... which has a uid which isn't present on the system: /zfs# chown testdir/test ... then an open() call with O_CREAT fails with Permission denied: /zfs# ./openat testdir/test Error opening testdir/test: Permission denied (13) Skip any of those steps and it doesn't throw the error. It's just that specific configuration of directory permissions and file ownership that seems to do it. The ./openat is a simple test case that just runs open() (so named as I was originally testing with the openat() call) and it's attached for reference. We have an rsync --inplace that gets us into that specific scenario. Dropping the --inplace works around it, FWIW, but then we lose a little space within the ZFS snapshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-aws-5.4/5.4.0-1020.20~18.04.2)
All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) 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-aws-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: New Status in linux source package in Precise: Fix Committed 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: New 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 1885757] Autopkgtest regression report (linux-aws-5.4/5.4.0-1020.20~18.04.2)
All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) 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-aws-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 in Ubuntu. https://bugs.launchpad.net/bugs/1885757 Title: seccomp_bpf fails on powerpc Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886668] Autopkgtest regression report (linux-aws-5.4/5.4.0-1020.20~18.04.2)
All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) 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-aws-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 in Ubuntu. https://bugs.launchpad.net/bugs/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] On systems using cgroups and sockets extensively, like docker, kubernetes, lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic. [Fix] Revert the patch that disables sk_alloc cgroup refcounting when tasks are added to net_prio cgroup. [Test case] Test that such environments where the issue is reproduced survive some hours of uptime. A different bug was reproduced with a work-in-progress code and was not reproduced with the culprit reverted. [Regression potential] The reverted commit fix a memory leak on similar scenarios. But a leak is better than a crash. Two other bugs have been opened to track a real fix for this issue and the leak. -- Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325] net_rx_ac
[Kernel-packages] [Bug 1884159] Autopkgtest regression report (linux-aws-5.4/5.4.0-1020.20~18.04.2)
All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) 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-aws-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 in Ubuntu. https://bugs.launchpad.net/bugs/1884159 Title: Update lockdown patches Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: Impact: The lockdown patches have evolved over time, and part of this was restricting more areas of the kernel. Not all of these additions were backported, and some can lead to lockdown bypasses, see [1] and [2]. Fix: Backport newer lockdown restrictions to older releases. Test Case: Test cases for most of the backports can be found at [3], and [4] is another test case. Some which need e.g. specific hardware to test have not been tested. Regression Potential: Most of these are small, simple fixes with low potential for regression. Users may also lose access to some functionality previously accissible under secure boot. Some changes are more substantial, especially the hw_param and debugfs changes for xenial, but they are based on well-tested upstream code. The xmon backports also carry a more moderate risk of regression. [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/ [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests [4] https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826848] Autopkgtest regression report (linux-aws-5.4/5.4.0-1020.20~18.04.2)
All autopkgtests for the newly accepted linux-aws-5.4 (5.4.0-1020.20~18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.9 (armhf) 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-aws-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 in Ubuntu. https://bugs.launchpad.net/bugs/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Failure to run ip_defrag deterministically. [Fix] Use smaller packets and ignore EPERM. [Test case] Run the test multiple times without observing failures. [Regression potential] If the test fix is incorrect, it will cause us to miss real kernel bugs. But as it is now, we are already ignoring its results. == Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
