[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Expired Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1881534] Re: Touchpad not working on Lenovo Thinkbook
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1881534 Title: Touchpad not working on Lenovo Thinkbook Status in linux package in Ubuntu: Expired Bug description: The touchpad on my Lenovo Thinkbook is not being detected at all. I have attached the devices list. I also tried installing ubuntu 20.04 and even in the latest version touchpad is not detected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889952] 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/1889952 Title: Trackpad undetected Lenovo ThinkBook 14-IML Status in linux package in Ubuntu: Confirmed Bug description: Trackpad does not work and is not present in cat /proc/bus/input/devices System Information Manufacturer: LENOVO Product Name: 20RV Version: Lenovo ThinkBook 14-IML SKU Number: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML Family: Lenovo ThinkBook 14-IML ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lombax21371 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 15:12:39 2020 InstallationDate: Installed on 2020-07-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=388a0ca2-1fc8-44cc-a513-a0c4b7786df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889952] [NEW] Trackpad undetected Lenovo ThinkBook 14-IML
Public bug reported: Trackpad does not work and is not present in cat /proc/bus/input/devices System Information Manufacturer: LENOVO Product Name: 20RV Version: Lenovo ThinkBook 14-IML SKU Number: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML Family: Lenovo ThinkBook 14-IML ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lombax21371 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 15:12:39 2020 InstallationDate: Installed on 2020-07-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=388a0ca2-1fc8-44cc-a513-a0c4b7786df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889952 Title: Trackpad undetected Lenovo ThinkBook 14-IML Status in linux package in Ubuntu: New Bug description: Trackpad does not work and is not present in cat /proc/bus/input/devices System Information Manufacturer: LENOVO Product Name: 20RV Version: Lenovo ThinkBook 14-IML SKU Number: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML Family: Lenovo ThinkBook 14-IML ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lombax21371 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 15:12:39 2020 InstallationDate: Installed on 2020-07-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20RV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=388a0ca2-1fc8-44cc-a513-a0c4b7786df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN29WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN29WW:bd06/19/2020:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
Ok I just did a quick test. It is writing to my xorg.conf. Also I noticed that when ubuntu starts up, on the login screen both screens have the purple background color - it's only after that when it gets to the desktop does the second display turn off. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: Won't Fix Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882834] Re: vmxnet3: update to latest ToT
So do we still have the following commits needed to patches to Ubuntu kernel ? vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 Thanks Yuhua Zou -- 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/1882834 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Confirmed Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you apply these patches to ongoing releases? Also, could you help verify if the below commits are present in vmxnet3 of ubuntu kernel? If not, then please apply these patches before above ones. vmxnet3: set the DMA mask before the first DMA map operation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd vmxnet3: use DMA memory barriers where required https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac vmxnet3: turn off lro when rxcsum is disabled https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Also affects: linux (Fedora) Importance: Undecided Status: New ** Changed in: linux (Arch Linux) Status: New => Confirmed ** Changed in: linux (Fedora) 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed 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
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
The workaround for me was to disable vt_handoff in /etc/grub.d/10_linux* (i.e. set vt_handoff=0 in both places near the top of the file). That resolved the issue completely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1
[Kernel-packages] [Bug 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
Unluckily this commit breaks hibernation:
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature"):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6
We should include the patch only if the kernel also includes
a4ddb11d297e ("video: hyperv: hyperv_fb: Support deferred IO for Hyper-V frame
buffer driver"
Now I'm seeing a hang/panic issue when hibernating the VM ("5.4.0-1022-azure
#22-Ubuntu"):
[ 67.736061] [ cut here ]
[ 67.736068] WARNING: CPU: 5 PID: 1358 at kernel/workqueue.c:3040
__flush_work+0x1b5/0x1d0
[ 67.736068] Modules linked in: xt_owner iptable_security xt_conntrack
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter nls_iso8859_1
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sb_edac crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper
joydev hid_generic hyperv_fb cfbfillrect hid_hyperv intel_rapl_perf serio_raw
hyperv_keyboard pata_acpi hv_netvsc hv_balloon hid cfbimgblt pci_hyperv
cfbcopyarea hv_utils pci_hyperv_intf sch_fq_codel drm
drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4
[ 67.736088] CPU: 5 PID: 1358 Comm: bash Not tainted 5.4.0-1022-azure
#22-Ubuntu
[ 67.736089] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 67.736091] RIP: 0010:__flush_work+0x1b5/0x1d0
[ 67.736092] Code: f0 eb e3 4d 8b 7c 24 20 e9 f3 fe ff ff 8b 0b 48 8b 53 08
83 e1 08 48 0f ba 2b 03 80 c9 f0 e9 4f ff ff ff 0f 0b e9 68 ff ff ff <0f> 0b 45
31 f6 e9 5e ff ff ff e8 ec e0 fd ff 66 66 2e 0f 1f 84 00
[ 67.736095] RSP: 0018:a7ce8a8ffb78 EFLAGS: 00010246
[ 67.736096] RAX: RBX: 8be3621f02a0 RCX:
[ 67.736096] RDX: 0001 RSI: 0001 RDI: 8be3621f02a0
[ 67.736097] RBP: a7ce8a8ffbf0 R08: R09: ff010101
[ 67.736098] R10: 8be363f7a320 R11: 0001 R12: 8be3621f02a0
[ 67.736098] R13: 0001 R14: 0001 R15: bc390fd1
[ 67.736099] FS: 7f6df35fe740() GS:8be375d4()
knlGS:
[ 67.736100] CS: 0010 DS: ES: CR0: 80050033
[ 67.736100] CR2: 561eef2c1b50 CR3: 000e40a14004 CR4: 001706e0
[ 67.736102] Call Trace:
[ 67.736108] __cancel_work_timer+0x107/0x180
[ 67.736119] cancel_delayed_work_sync+0x13/0x20
[ 67.736121] hvfb_suspend+0x48/0x80 [hyperv_fb]
[ 67.736122] vmbus_suspend+0x2a/0x40
[ 67.736125] dpm_run_callback+0x5b/0x150
[ 67.736127] __device_suspend_noirq+0x9e/0x2f0
[ 67.736128] dpm_suspend_noirq+0x101/0x2d0
[ 67.736130] dpm_suspend_end+0x53/0x80
[ 67.736132] hibernation_snapshot+0xd8/0x460
[ 67.736133] hibernate.cold+0x6d/0x1f6
[ 67.736135] state_store+0xde/0xe0
[ 67.736138] kobj_attr_store+0x12/0x20
[ 67.736141] sysfs_kf_write+0x3e/0x50
[ 67.736142] kernfs_fop_write+0xda/0x1b0
[ 67.736145] __vfs_write+0x1b/0x40
[ 67.736147] vfs_write+0xb9/0x1a0
[ 67.736149] ksys_write+0x67/0xe0
[ 67.736150] __x64_sys_write+0x1a/0x20
[ 67.736152] do_syscall_64+0x5e/0x200
[ 67.736156] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 67.736157] RIP: 0033:0x7f6df3712057
After I revert 0a14dbaa0736, hibernation works.
--
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/1880032
Title:
[linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Released
Bug description:
Microsoft would like to request commits to enable VM hibernation in
the Azure 5.4 kernels for 18.04 and 20.04.
Some of the commits needed to enable VM hibernation were included in
mainline 5.4 and older. However, 24 commits were added in 5.5 and
later, which are required in the 5.4 kernel. The list of commits
requested are:
38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment
notifications
2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume()
421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation
1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM
3704a6a44579 PM: hibernate: Propagate the return value of
hibernation_restore()
54e19d34011f hv_utils: Add the support of hibernation
ffd1d4a49336 hv_utils: Support host-initiated hibernation request
3e9c72056ed5 hv_utils: Support host-initiated restart request
9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns
05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation
382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature
e2379b30324c Input:
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
> My default first boot device is Ubuntu and then windows and then USB and network.. etc.. (...) > I tried to run pratation magic. How did you boot Partition Magic? If this is on a DVD, the ODD must be before the HDD in the boot sequence. Then you could also just boot Focal64 for fixing. -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015
[Kernel-packages] [Bug 1882624] Re: nested kvm doesn't work
Hi, Lili. I think this new problem is caused by the older qemu version that we have in trusty. Does it work without the -cpu host argument? -- 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/1882624 Title: nested kvm doesn't work Status in linux-azure package in Ubuntu: New Bug description: Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using size Standard E4s v3 Enable private-ppa canonical-kernel-esm Install kernel linux-azure, reboot VM, kernel version 4.15.0-1084-azure Install qemu-kvm, download https://eosgnestedstorage.blob.core.windows.net/images/nested- ubuntu-4.15.0-23-generic.qcow2 Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize Expected ssh -p 60022 nesteduser@localhost will ask password to login We can't connect to it, see below call trace in dmesg qemu-kvm version doesn't change after kernel upgraded. 2.0.0+dfsg-2ubuntu1.46 [ 53.420589] hv_balloon: Max. dynamic memory size: 32768 MB [ 60.928772] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. [ 60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable [ 60.967454] BUG: unable to handle kernel paging request at 56b8 [ 60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] PGD 0 P4D 0 [ 60.971140] Oops: [#1] SMP PTI [ 60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils [ 60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 4.15.0-1084-azure #94~14.04.1-Ubuntu [ 60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002 [ 60.971140] RAX: RBX: RCX: [ 61.020070] RDX: 6c14 RSI: RDI: [ 61.020070] RBP: a44847a53d10 R08: R09: [ 61.020070] R10: R11: R12: [ 61.020070] R13: R14: R15: [ 61.020070] FS: 7f753bba4700() GS:8fefdd68() knlGS: [ 61.020070] CS: 0010 DS: ES: CR0: 80050033 [ 61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 003726e0 [ 61.020070] Call Trace: [ 61.020070] vcpu_enter_guest+0x909/0x12a0 [kvm] [ 61.020070] kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm] [ 61.020070] kvm_vcpu_ioctl+0x2a8/0x630 [kvm] [ 61.020070] ? dequeue_signal+0x3e/0x160 [ 61.020070] ? do_sigtimedwait+0xbd/0x210 [ 61.020070] ? copy_siginfo_to_user+0x12e/0x2d0 [ 61.020070] do_vfs_ioctl+0x9b/0x5f0 [ 61.020070] ? SyS_futex+0x71/0x150 [ 61.020070] SyS_ioctl+0x79/0x90 [ 61.020070] ? _copy_to_user+0x26/0x40 [ 61.020070] do_syscall_64+0x80/0x1e0 [ 61.020070] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 61.020070] RIP: 0033:0x7f7545f34ea7 [ 61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 0010 [ 61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 7f7545f34ea7 [ 61.020070] RDX: RSI: ae80 RDI: 000c [ 61.020070] RBP: 55c68fd7f160 R08: R09: 0002 [ 61.020070] R10: 0008 R11: 0246 R12: [ 61.020070] R13: R14: 7f753bba49c0 R15: 55c68ee809a0 [ 61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01 [ 61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0 [ 61.020070] CR2: 56b8 [ 61.020070] ---[ end trace ab52be3a09d557f5 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1883012] Re: CPU stuck for 22s
The freeze happened again, despite the UEFI setting "Typical Current Idle". It happened after display energy saving after the wakeup. ** Attachment added: "freeze_31_july_2020.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883012/+attachment/5397562/+files/freeze_31_july_2020.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/1883012 Title: CPU stuck for 22s Status in linux package in Ubuntu: Confirmed Bug description: I get regularly system freezes, so that nothing works anymore. The only thing I can do, is a hard reset. These are the last kernel logs: Jun 10 21:34:47 stefano-linux anacron[6995]: Anacron 2.3 started on 2020-06-10 Jun 10 21:34:47 stefano-linux anacron[6995]: Normal exit (0 jobs run) Jun 10 21:35:41 stefano-linux rtkit-daemon[1169]: Supervising 12 threads of 8 processes of 2 users. Jun 10 21:35:41 stefano-linux rtkit-daemon[1169]: Supervising 12 threads of 8 processes of 2 users. Jun 10 21:39:03 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:39:16 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:42:43 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:42:57 stefano-linux gnome-shell[2281]: ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost Jun 10 21:47:41 stefano-linux kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [JS Helper:2153] Jun 10 21:47:41 stefano-linux kernel: Modules linked in: snd_usb_audio snd_usbmidi_lib gspca_vc032x uvcvideo gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc snd_hda_codec_hdmi edac_mce_amd kvm_amd kvm nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(> Jun 10 21:47:41 stefano-linux kernel: CPU: 1 PID: 2153 Comm: JS Helper Tainted: P O 5.4.0-37-generic #41-Ubuntu Jun 10 21:47:41 stefano-linux kernel: Hardware name: System manufacturer System Product Name/PRIME B350-PLUS, BIOS 5407 12/31/2019 Jun 10 21:47:41 stefano-linux kernel: RIP: 0010:smp_call_function_many+0x203/0x270 Jun 10 21:47:41 stefano-linux kernel: Code: 73 08 e8 90 0e 96 00 3b 05 5e d4 6f 01 89 c7 0f 83 9b fe ff ff 48 63 c7 48 8b 0b 48 03 0c c5 80 59 04 9e 8b 41 18 a8 01 74 0a 90 8b 51 18 83 e2 01 75 f6 eb c8 89 cf 48 c7 c2 60 ae 44 9e 4c Jun 10 21:47:41 stefano-linux kernel: RSP: 0018:98bc02edbb58 EFLAGS: 0202 ORIG_RAX: ff13 Jun 10 21:47:41 stefano-linux kernel: RAX: 0003 RBX: 8890ce86bc80 RCX: b8bbfe817680 Jun 10 21:47:41 stefano-linux kernel: RDX: 0001 RSI: RDI: 0008 Jun 10 21:47:41 stefano-linux kernel: RBP: 98bc02edbb98 R08: 8890bfedc788 R09: 8890bfedc018 Jun 10 21:47:41 stefano-linux kernel: R10: 8890bfedc788 R11: R12: 9cc88c80 Jun 10 21:47:41 stefano-linux kernel: R13: 8890ce86a640 R14: 0001 R15: 0020 Jun 10 21:47:41 stefano-linux kernel: FS: 7f3c91505700() GS:8890ce84() knlGS: Jun 10 21:47:41 stefano-linux kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 10 21:47:41 stefano-linux kernel: CR2: 7fdb7324afe0 CR3: 000396ff CR4: 003406e0 Jun 10 21:47:41 stefano-linux kernel: Call Trace: Jun 10 21:47:41 stefano-linux kernel: native_flush_tlb_others+0x55/0x170 Jun 10 21:47:41 stefano-linux kernel: flush_tlb_mm_range+0xb4/0xe0 Jun 10 21:47:41 stefano-linux kernel: tlb_flush_mmu+0xb0/0x140 Jun 10 21:47:41 stefano-linux kernel: tlb_finish_mmu+0x42/0x80 Jun 10 21:47:41 stefano-linux kernel: unmap_region+0xf9/0x130 Jun 10 21:47:41 stefano-linux kernel: __do_munmap+0x291/0x4c0 Jun 10 21:47:41 stefano-linux kernel: mmap_region+0x240/0x670 Jun 10 21:47:41 stefano-linux kernel: do_mmap+0x3b4/0x5c0 Jun 10 21:47:41 stefano-linux kernel: vm_mmap_pgoff+0xcb/0x120 Jun 10 21:47:41 stefano-linux kernel: ksys_mmap_pgoff+0x5b/0x2a0 Jun 10 21:47:41 stefano-linux kernel: ? free_cpumask_var+0x9/0x10 Jun 10 21:47:41 stefano-linux kernel: __x64_sys_mmap+0x33/0x40 Jun 10 21:47:41 stefano-linux kernel: do_syscall_64+0x57/0x190 Jun 10 21:47:41 stefano-linux kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 10 21:47:41 stefano-linux kernel: RIP: 0033:0x7f3ca311f70d Jun 10 21:47:41 stefano-linux kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 f7 0c 00 f7 d8 64 89 01 48 Jun 10 21:47:41 stefano-linux kernel: RSP: 002b:7f3c91504b08 EFLAGS:
Re: [Kernel-packages] [Bug 1888894] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically
Hi Thank you I am no longer really having issues with the wifi. I think its actually fixed or something from an update. I dont see anything in the dmesg logs. you can close this ticket. On 2020-07-31 3:19 p.m., Alex Hung wrote: > Performance degrades can also related to power saving. Try kernel > parameter "pcie_aspm=off" to verify whether it improves > -- 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/194 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically Status in linux package in Ubuntu: Confirmed Bug description: Hello, For the past several months, I noticed my wifi just drops periodically. Disabling bluetooth reduces the frequency of this. Also Ive noticed speed is slower on wifi for my 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). this problem affects others too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1741 F pulseaudio /dev/snd/controlC0: steve 1741 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-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: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
Actually looking at the patch (shrink_dcache_for_umount) this might not be the whole problem but may be just related. The problem I am having is while the system is still running, and cache growing huge, not while umounting. -- 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
The last time I got it to hang long enough to produce a backtrace it showed: [1560556.660010] INFO: task vgs:3103183 blocked for more than 1105 seconds. [1560556.660012] Tainted: G U OE 5.4.0-40-lowlatency #44-Ubuntu [1560556.660013] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1560556.660014] vgs D0 3103183 411358 0x80004004 [1560556.660016] Call Trace: [1560556.660021] __schedule+0x2e5/0x750 [1560556.660023] schedule+0x49/0xd0 [1560556.660024] schedule_timeout+0x21a/0x300 [1560556.660027] ? call_rcu+0x10/0x20 [1560556.660030] ? __percpu_ref_switch_mode+0xec/0x1b0 [1560556.660031] wait_for_completion+0xa3/0x100 [1560556.660033] ? wake_up_q+0x70/0x70 [1560556.660036] exit_aio+0xe7/0xf0 [1560556.660038] mmput+0x22/0x120 [1560556.660039] do_exit+0x2f8/0xae0 [1560556.660041] ? finish_task_switch+0x75/0x250 [1560556.660042] do_group_exit+0x43/0xa0 [1560556.660044] get_signal+0x13e/0x8f0 [1560556.660046] ? hrtimer_cancel+0x15/0x20 [1560556.660047] ? read_events+0x14f/0x160 [1560556.660049] do_signal+0x34/0x6e0 [1560556.660050] ? hrtimer_init_sleeper+0xb0/0xb0 [1560556.660052] ? do_io_getevents+0x7a/0xf0 [1560556.660054] exit_to_usermode_loop+0xbf/0x160 [1560556.660055] do_syscall_64+0x163/0x190 [1560556.660057] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1560556.660058] RIP: 0033:0x7f3b1269a70d [1560556.660062] Code: Bad RIP value. [1560556.660062] RSP: 002b:7fffd99f2f08 EFLAGS: 0246 ORIG_RAX: 00d0 [1560556.660064] RAX: fffc RBX: 7f3b1228e6c0 RCX: 7f3b1269a70d [1560556.660064] RDX: 0040 RSI: 0001 RDI: 7f3b12a7e000 [1560556.660065] RBP: 7f3b12a7e000 R08: R09: 00020016 [1560556.660065] R10: 7fffd99f2f90 R11: 0246 R12: 0001 [1560556.660066] R13: 0002 R14: 0040 R15: 7fffd99f2f90 -- 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard:
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
It appears Red Hat fixed this problem with a kernel patch in RHEL 7.5 that was not upstreamed. https://access.redhat.com/errata/RHSA-2018:1062 BZ - 1471875 - soft lockups during unmount when dentry cache is very large https://bugzilla.redhat.com/show_bug.cgi?id=1471875 ** Bug watch added: Red Hat Bugzilla #1471875 https://bugzilla.redhat.com/show_bug.cgi?id=1471875 -- 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co.,
[Kernel-packages] [Bug 1888894] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically
Performance degrades can also related to power saving. Try kernel parameter "pcie_aspm=off" to verify whether it improves -- 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/194 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically Status in linux package in Ubuntu: Confirmed Bug description: Hello, For the past several months, I noticed my wifi just drops periodically. Disabling bluetooth reduces the frequency of this. Also Ive noticed speed is slower on wifi for my 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). this problem affects others too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1741 F pulseaudio /dev/snd/controlC0: steve 1741 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-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: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889928] [NEW] Xenial update: v4.4.232 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v4.4.232 upstream stable release
from git://git.kernel.org/
pinctrl: amd: fix npins for uart0 in kerncz_groups
mac80211: allow rx of mesh eapol frames with default rx key
scsi: scsi_transport_spi: Fix function pointer check
xtensa: fix __sync_fetch_and_{and,or}_4 declarations
xtensa: update *pos in cpuinfo_op.next
drivers/net/wan/lapbether: Fixed the value of hard_header_len
net: sky2: initialize return of gm_phy_read
drm/nouveau/i2c/g94-: increase NV_PMGR_DP_AUXCTL_TRANSACTREQ timeout
SUNRPC reverting d03727b248d0 ("NFSv4 fix CLOSE not waiting for direct IO
compeletion")
perf/core: Fix locking for children siblings group read
uprobes: Change handle_swbp() to send SIGTRAP with si_code=SI_KERNEL, to fix
GDB regression
ALSA: info: Drop WARN_ON() from buffer NULL sanity check
ASoC: rt5670: Correct RT5670_LDO_SEL_MASK
btrfs: fix double free on ulist after backref resolution failure
x86/fpu: Disable bottom halves while loading FPU registers
btrfs: fix mount failure caused by race with umount
hippi: Fix a size used in a 'pci_free_consistent()' in an error handling path
ax88172a: fix ax88172a_unbind() failures
net: dp83640: fix SIOCSHWTSTAMP to update the struct with actual configuration
net: smc91x: Fix possible memory leak in smc_drv_probe()
scripts/decode_stacktrace: strip basepath from all paths
regmap: dev_get_regmap_match(): fix string comparison
usb: gadget: udc: gr_udc: fix memleak on error handling path in gr_ep_init()
arm64: Use test_tsk_thread_flag() for checking TIF_SINGLESTEP
x86: math-emu: Fix up 'cmp' insn for clang ias
Revert "cifs: Fix the target file was deleted when rename failed."
staging: wlan-ng: properly check endpoint types
staging: comedi: addi_apci_1032: check INSN_CONFIG_DIGITAL_TRIG shift
staging: comedi: ni_6527: fix INSN_CONFIG_DIGITAL_TRIG support
staging: comedi: addi_apci_1500: check INSN_CONFIG_DIGITAL_TRIG shift
staging: comedi: addi_apci_1564: check INSN_CONFIG_DIGITAL_TRIG shift
serial: 8250: fix null-ptr-deref in serial8250_start_tx()
serial: 8250_mtk: Fix high-speed baud rates clamping
mm/memcg: fix refcount error while moving and swapping
parisc: Add atomic64_set_release() define to avoid CPU soft lockups
ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
ath9k: Fix regression with Atheros 9271
AX.25: Fix out-of-bounds read in ax25_connect()
AX.25: Prevent out-of-bounds read in ax25_sendmsg()
net-sysfs: add a newline when printing 'tx_timeout' by sysfs
net: udp: Fix wrong clean up for IS_UDPLITE macro
AX.25: Prevent integer overflows in connect and sendmsg
tcp: allow at most one TLP probe per flight
rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA
ip6_gre: fix null-ptr-deref in ip6gre_init_net()
drivers/net/wan/x25_asy: Fix to make it work
Makefile: Fix GCC_TOOLCHAIN_DIR prefix for Clang cross compilation
regmap: debugfs: check count when read regmap file
xfs: set format back to extents if xfs_bmap_extents_to_btree
tools/lib/subcmd/pager.c: do not alias select() params
perf: Make perf able to build with latest libbfd
perf tools: Fix snprint warnings for gcc 8
perf annotate: Use asprintf when formatting objdump command line
perf probe: Fix to check blacklist address correctly
Linux 4.4.232
UBUNTU: upstream stable to v4.4.232
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process,
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
I haven't verified if this actually fixes the problem but it seems to make a huge difference in 'free' memory as shown by 'free'. I had already closed my VMs by the time I tried this so haven't verified if it stops the long freezes yet. totalusedfree shared buff/cache available Mem: 31030533127905347 22907 19900 Swap: 327673130 29637 echo 3 > /proc/sys/vm/drop_caches totalusedfree shared buff/cache available Mem: 310305349 1712253128557 19915 Swap: 327673130 29637 Notice the 2790 -> 17122 change above in 'free', and 22907 -> 8557 for buff/cache. It appears the kernel doesn't get rid of cache in a reasonable timeframe at the expense of swapping programs out to disk while i/o is happening, which causes gui freezes. -- 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star
[Kernel-packages] [Bug 1889926] [NEW] Can't access gpio mapped memory on focal armhf server on pi
Public bug reported:
On released (and apt updated) 20.04 armhf preinstalled server on Pi3B+,
we cannot use pigpio C program to access memory map for gpio. Customer
says the same code works fine on 18.04.
ubuntu@ubuntu:~$ sudo ./pigpio/kyle.o
2020-07-31 18:36:11 initPeripherals: mmap gpio failed (Operation not permitted)
Details on code below, but the executable is attached, and the customer
says this fairly represents their code usage.
ubuntu@ubuntu:~/pigpio$ uname -a
Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020
armv7l armv7l armv7l GNU/Linux
We thought perhaps these kernel configs were involved:
CONFIG_DEVMEM=y
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
... and we modified the kernel cmdline with the following, but the result was
the same.
iomem=relaxed strict-devmem=0
The program is simply this https://github.com/joan2937/pigpio/ with make & make
install
then this c file:
#include
#include
#include
int main(void){
gpioInitialise();
}
built with gcc -Wall -I/home/ubuntu/pigpio -pthread -o kyle.o kyle.c
-lpigpio -lrt
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "kyle.o"
https://bugs.launchpad.net/bugs/1889926/+attachment/5397526/+files/kyle.o
** Description changed:
On released (and apt updated) 20.04 armhf preinstalled server on Pi3B+,
- we cannot use pigpio C program to access memory map for gpio.
+ we cannot use pigpio C program to access memory map for gpio. Customer
+ says the same code works fine on 18.04.
- ubuntu@ubuntu:~$ sudo ./pigpio/kyle.o
+ ubuntu@ubuntu:~$ sudo ./pigpio/kyle.o
2020-07-31 18:36:11 initPeripherals: mmap gpio failed (Operation not
permitted)
Details on code below, but the executable is attached, and the customer
says this fairly represents their code usage.
ubuntu@ubuntu:~/pigpio$ uname -a
Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020
armv7l armv7l armv7l GNU/Linux
We thought perhaps these kernel configs were involved:
CONFIG_DEVMEM=y
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
... and we modified the kernel cmdline with the following, but the result was
the same.
iomem=relaxed strict-devmem=0
The program is simply this https://github.com/joan2937/pigpio/ with make &
make install
then this c file:
#include
#include
#include
int main(void){
gpioInitialise();
}
built with gcc -Wall -I/home/ubuntu/pigpio -pthread -o kyle.o kyle.c
-lpigpio -lrt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1889926
Title:
Can't access gpio mapped memory on focal armhf server on pi
Status in linux-raspi package in Ubuntu:
New
Bug description:
On released (and apt updated) 20.04 armhf preinstalled server on
Pi3B+, we cannot use pigpio C program to access memory map for gpio.
Customer says the same code works fine on 18.04.
ubuntu@ubuntu:~$ sudo ./pigpio/kyle.o
2020-07-31 18:36:11 initPeripherals: mmap gpio failed (Operation not
permitted)
Details on code below, but the executable is attached, and the
customer says this fairly represents their code usage.
ubuntu@ubuntu:~/pigpio$ uname -a
Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020
armv7l armv7l armv7l GNU/Linux
We thought perhaps these kernel configs were involved:
CONFIG_DEVMEM=y
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
... and we modified the kernel cmdline with the following, but the result was
the same.
iomem=relaxed strict-devmem=0
The program is simply this https://github.com/joan2937/pigpio/ with make &
make install
then this c file:
#include
#include
#include
int main(void){
gpioInitialise();
}
built with gcc -Wall -I/home/ubuntu/pigpio -pthread -o kyle.o kyle.c
-lpigpio -lrt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889926/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
I am going to work out on a change to the default crashkernel value on s390x to match what we do for ppc64el. That will improve the situation on default installations. ** Changed in: makedumpfile (Ubuntu Groovy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: makedumpfile (Ubuntu Groovy) Status: Won't Fix => In Progress ** Changed in: makedumpfile (Ubuntu Focal) Status: Won't Fix => Confirmed ** Changed in: makedumpfile (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Confirmed Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887294] Re: [nvidia] Display freeze
It occurred once more, after about 19 days uptime. There's an entry about Xorg in the dmesg that could be interesting, and the full dmesg is attached. [1638952.386233] Xorg: page allocation failure: order:4, mode:0x40cc0(GFP_KERNEL|__GFP_COMP), nodemask=(null),cpuset=/,mems_allowed=0 ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+attachment/5397525/+files/dmesg.txt -- 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/1887294 Title: [nvidia] Display freeze Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
I have this problem as well on Cinnamon, so it doesn't appear to be specific to KDE. It stalls often and frequently over 15-30 seconds at a time for no apparent reason. But the swapping to disk may be a clue. I see this on 5.4.0-40 and have also tried with the lowlatency version of the kernel and it doesn't help. One thing that seems to reduce the frequency of the problem somewhat is to disable transparent_hugepage support but it still happens even after that. I have 32GB ram and it starts happening when I get to about 50% ram (mem available) usage. The system also appears to start swapping at that point despite what swappiness is set to. I tried setting it to 10 but it is still swapping at what appears to be ~ 50% usage. It appears to be very easy to reproduce if you run a few VMware VMs on a system. # cat /proc/sys/vm/swappiness 10 $ free -m totalusedfree shared buff/cache available Mem: 310306591 2469050 24192 14936 Swap: 327674942 27825 $ cat /proc/meminfo MemTotal: 31774792 kB MemFree: 256768 kB MemAvailable: 15324804 kB Buffers: 5887324 kB Cached: 16712984 kB SwapCached: 488276 kB Active: 19816476 kB Inactive:8835508 kB Active(anon): 12801324 kB Inactive(anon): 2522936 kB Active(file):7015152 kB Inactive(file): 6312572 kB Unevictable: 145612 kB Mlocked: 48 kB SwapTotal: 33554428 kB SwapFree: 28493052 kB Dirty: 2301336 kB Writeback: 9564 kB AnonPages: 6161528 kB Mapped: 7931416 kB Shmem: 9272240 kB KReclaimable:2201904 kB Slab:2451272 kB SReclaimable:2201904 kB SUnreclaim: 249368 kB KernelStack: 21552 kB PageTables:85272 kB NFS_Unstable: 0 kB Bounce:0 kB WritebackTmp: 0 kB CommitLimit:49441824 kB Committed_AS: 30098296 kB VmallocTotal: 34359738367 kB VmallocUsed: 55400 kB VmallocChunk: 0 kB Percpu: 7712 kB HardwareCorrupted: 0 kB AnonHugePages: 0 kB ShmemHugePages:0 kB ShmemPmdMapped:0 kB FileHugePages: 0 kB FilePmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 5078656 kB DirectMap2M:27346944 kB DirectMap1G: 0 kB ** Changed in: linux (Ubuntu) Status: Invalid => 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks
[Kernel-packages] [Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
Thanks for the analysis! systemd appears to set this value in: ./sysctl.d/50-pid-max.conf:kernel.pid_max = 4194304 One possible solution is we could override this in our minimal images only by setting the value to the lower value in /etc/sysctl.d/90-override.conf ** Also affects: cloud-images 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/1888001 Title: Focal minimal cloud image: failed to apply kernel variables Status in cloud-images: New Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Focal minimal images have always shipped with a failing systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' to 'kernel/pid_max': Invalid argument" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables From the journal: Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit ed, code=exited, status=1/FAILURE Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile d with result 'exit-code'. Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables. Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker nel/pid_max': Invalid argument Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img --name=focal-minimal $ multipass exec focal-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-1018-kvm N/A linux-backports-modules-5.4.0-1018-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1018-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1888001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
Based on the update above, #17, I am adding the open-iscsi package task. ** Also affects: open-iscsi (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/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Bug description: Overview --- It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Also affects: linux (Arch Linux) 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: 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
[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 here. Thank you guys for finding a fix ;) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1711283] Re: few kernel selftest failed on Ubuntu 17.10
This problem seems to be fixed in more recent release - ug can be closed -- 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/1711283 Title: few kernel selftest failed on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: == Comment: #0 - Harish Sriram - 2017-08-01 05:11:09 == Problem Description Few kernel selftest failed on Ubuntu 17.10 Environment -- Kernel Build: 4.11.0-10-generic System Name : ltc-test-ci2 Model : 8247-22L Platform: PowerNV ( P8 ) Uname output --- # uname -a Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Get kernel source using apt source 2. Start powerpc specific tests The following FAILS are observed. selftests: cycles_test [FAIL] selftests: cycles_with_freeze_test [FAIL] selftests: pmc56_overflow_test [FAIL] selftests: ebb_vs_cpu_event_test [FAIL] selftests: cpu_event_vs_ebb_test [FAIL] selftests: task_event_vs_ebb_test [FAIL] selftests: multi_ebb_procs_test [FAIL] selftests: multi_counter_test [FAIL] selftests: pmae_handling_test [FAIL] selftests: close_clears_pmcc_test [FAIL] selftests: instruction_count_test [FAIL] selftests: ebb_on_willing_child_test [FAIL] selftests: back_to_back_ebbs_test [FAIL] selftests: lost_exception_test [FAIL] selftests: cycles_with_mmcr2_test [FAIL] selftests: tm-vmxcopy [FAIL] Full run log is attached. == Comment: #5 - Harish Sriram - 2017-08-08 03:33:36 == With the latest ubuntu mainline kernel 4.13-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following additional failures selftests: ptrace-gpr [FAIL] selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr [FAIL] # uname -a Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Thanks, Harish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
This is because CONFIG_BASE_SMALL is set to 1 in the kvm kernels. When CONFIG_BASE_SMALL=1, the maximum number of PIDs is (PAGE_SIZE * 8), which comes out to (4096 * 8) = 32768 on amd64. When CONFIG_BASE_SMALL=0 (like in normal kernels), the maximum number of PIDs for amd64 is (4 * 1024 * 1024) = 4194304. The correct solution here is to fix the systemd unit. -- 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/1888001 Title: Focal minimal cloud image: failed to apply kernel variables Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Focal minimal images have always shipped with a failing systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' to 'kernel/pid_max': Invalid argument" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables From the journal: Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit ed, code=exited, status=1/FAILURE Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile d with result 'exit-code'. Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables. Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker nel/pid_max': Invalid argument Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img --name=focal-minimal $ multipass exec focal-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-1018-kvm N/A linux-backports-modules-5.4.0-1018-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1018-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
This is a bug in the open-iscsi package in xenial and bionic. That package installs this file: /lib/modules-load.d/open-iscsi.conf Which contains the following: iscsi_tcp ib_iser This causes systemd to always try and load the iscsi_tcp and ib_iser modules on boot. In eoan, the open-iscsi package doesn't do this; there's no /lib/modules-load.d/open-iscsi.conf file in the eoan cloud image. An update to xenial/bionic open-iscsi packages to match the behavior of eoan's open-iscsi package should resolve this I think. -- 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/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478]
I have the same problem on my Thinkpad x240 with Ubuntu 20.04 Linux E5450 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux This kernel parameter workaround "psmouse.synaptics_intertouch=0" work in the meantime (forever since it's 3 years old bug ??) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Confirmed on Linux 5.4.0-42-generic with Linux Mint 20 (Ubuntu 20.04) clean install. Changing lz4 to gzip in /etc/initramfs-tools/initramfs.conf removed the error (after doing sudo update-initramfs -u) -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install
I’ve also had some issues with the audio, but I’ve been able to fix that up by fiddling with pulseaudio. Re the bug fix, should I try a clean install? This isn’t optimal since I’m mostly set up now, but would this help the bug fix take effect? On Thu, Jul 30, 2020 at 9:05 PM Daniel van Vugt <1888...@bugs.launchpad.net> wrote: > In the past "ice-lake-flicker" issues have been related to the audio > system(!). That was supposedly fixed in bug 1875254, but your log shows > some errors in the same area: > > [ 117.852074] sof-audio-pci :00:1f.3: error: no reply expected, > received 0x0 > [ 117.944970] sof-audio-pci :00:1f.3: firmware boot complete > [ 170.252664] sof-audio-pci :00:1f.3: error: no reply expected, > received 0x0 > [ 170.347691] sof-audio-pci :00:1f.3: firmware boot complete > [ 235.442471] sof-audio-pci :00:1f.3: error: no reply expected, > received 0x0 > [ 235.537670] sof-audio-pci :00:1f.3: firmware boot complete > ... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888571 > > Title: > [Ice Lake] Screen flickering and glitching after install > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Intel integrated driver causes screen flickering with Ubuntu install. > Windows did not have this issue > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Jul 22 15:41:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if > 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] > InstallationDate: Installed on 2020-07-22 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: HP HP ENVY Laptop 13-ba0xxx > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/04/2020 > dmi.bios.vendor: Insyde > dmi.bios.version: F.10 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 875A > dmi.board.vendor: HP > dmi.board.version: 07.34 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Envy > dmi.product.name: HP ENVY Laptop 13-ba0xxx > dmi.product.sku: 8KD13AV > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+subscriptions > -- Drew Erikson University of Minnesota - Twin Cities Computer Science & Mathematics | 2020 eriks...@umn.edu -- 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop:
[Kernel-packages] [Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
It seems update 435.21-0ubuntu0.18.04.3 of nvidia-kernel-source-435 fixed the problem for me, at least! -- 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/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: 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-435/+bug/1888617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Marcelo Pires (marcelo-pires-silva) -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Hui, is there a guide/checklist how to test the Pi OS kernel on Ubuntu? I trie replacing the contents of the FAT partition, and the kernel did boot, but that's still missing the modules, possibly something else..? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) Status in linux-raspi2 package in Ubuntu: Incomplete Status in linux-raspi2 source package in Eoan: Confirmed Status in linux-raspi2 source package in Focal: Confirmed Bug description: Desciption changed: Raspberry Pi 3 network partially dies (transmission doesn't work, reception still does) shortly after a burst of network load over IPv6, when IPv6 connectivity is provided by a tunnel from tunnelbroker.net. The triggering load is typically an HTTP(S) download, and replication can be done without actually saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 GB, usually withinthe first 1 GB of traffic) Replication is 100% as long as _all_ of the following conditions are met - 6in4 tunnel to HE.net set up with netplan - ipv6 rules applied (netfilter-persistent) - ipv6 forwarding enabled (edit /etc/sysctl.conf) kern.log message that appears after a while: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4
[Kernel-packages] [Bug 1888691] Re: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps
I've confirmed that this is the case. The Pi refreshes the kernel to 179, reboots and tries to run the 179 kernel with the 156 DTBs. We're not maintaining DTB backwards compatibility, so not a kernel problem. ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1888691 Title: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps Status in snapd: New Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: Invalid Bug description: The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does not boot. After it gets to "Starting kernel..." it just stops. Attempting to power off/on the device after the failed boot fails in the uboot script: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 28 ms (161.1 KiB/s) ## Executing script at 0240 4096 bytes read in 39 ms (102.5 KiB/s) 131072 bytes read in 45 ms (2.8 MiB/s) 131072 bytes written in 89 ms (1.4 MiB/s) SCRIPT FAILED: continuing... 45618 bytes read in 41 ms (1.1 MiB/s) Card did not respond to voltage select! starting USB... ... This does not seem to happen with the arm64 kernel, and booting the armhf kernel seems to work fine on pi3 devices - it just seems to be the combination of armhf and rpi4 that breaks right now. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1888691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889761] Re: [UBUNTU 20.04] nfs storage failed to run on top of kubernetes-core cluster on s390x
** Package changed: linux (Ubuntu) => cdk ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: cdk Assignee: Skipper Bug Screeners (skipper-screen-team) => CDK (cdk8s) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- 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/1889761 Title: [UBUNTU 20.04] nfs storage failed to run on top of kubernetes-core cluster on s390x Status in CDK: New Status in Ubuntu on IBM z Systems: New Bug description: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Install nfs as it is mentioned at https://ubuntu.com/kubernetes/docs/storage juju deploy nfs --constraints root-disk=10G juju add-relation nfs kubernetes-worker Expected result: `kubectl get sc,po` will show running pod and storage class Actual result: # kubectl get sc,po NAMEPROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE storageclass.storage.k8s.io/default (default) fuseim.pri/ifs Delete Immediate false 2m17s NAME READY STATUS RESTARTS AGE pod/nfs-client-provisioner-7698b8dbc9-wj56n 0/1 ContainerCreating 0 2m17s # kubectl describe pod nfs-client-provisioner-7698b8dbc9-wj56n Name: nfs-client-provisioner-7698b8dbc9-wj56n Namespace: default Priority: 0 Node: juju-62238e-2/10.70.13.80 Start Time: Fri, 31 Jul 2020 11:39:19 +0200 Labels: app=nfs-client-provisioner pod-template-hash=7698b8dbc9 Annotations: Status: Pending IP: IPs: Controlled By: ReplicaSet/nfs-client-provisioner-7698b8dbc9 Containers: nfs-client-provisioner: Container ID: Image: rocks.canonical.com:443/cdk/external_storage/nfs-client-provisioner:v3.1.0-k8s1.11 Image ID: Port: Host Port: State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Environment: PROVISIONER_NAME: fuseim.pri/ifs NFS_SERVER:10.70.13.33 NFS_PATH: /srv/data/kubernetes-worker Mounts: /persistentvolumes from nfs-client-root (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-r2qgb (ro) Conditions: Type Status Initialized True Ready False ContainersReady False PodScheduled True Volumes: nfs-client-root: Type: NFS (an NFS mount that lasts the lifetime of a pod) Server:10.70.13.33 Path: /srv/data/kubernetes-worker ReadOnly: false default-token-r2qgb: Type:Secret (a volume populated by a Secret) SecretName: default-token-r2qgb Optional:false QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason AgeFromMessage -- --- Normal Scheduled default-scheduler Successfully assigned default/nfs-client-provisioner-7698b8dbc9-wj56n to juju-62238e-2 Warning FailedMount 2m58s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root --scope -- mount -t nfs 10.70.13.33:/srv/data/kubernetes-worker /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root Output: Running scope as unit: run-r946191ed443941e5ad6dcc42ede13325.scope mount.nfs: requested NFS version or transport protocol is not supported Warning FailedMount 2m57s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root --scope -- mount -t nfs 10.70.13.33:/srv/data/kubernetes-worker
[Kernel-packages] [Bug 1889763] [NEW] [UBUNTU 20.04] kubernetes-core is not fully installed on s390x
Public bug reported: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Expected result - 1 master and 1 worker node. Actual result - just 1 node. # juju status Model Controller Cloud/Region Version SLA Timestamp k8slocalhost-localhost localhost/localhost 2.8.1unsupported 11:28:37+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3active 2 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsajujucharms 318 ubuntu etcd 3.3.19 active 1 etcd jujucharms 521 ubuntu flannel0.11.0 active 2 flanneljujucharms 492 ubuntu kubernetes-master 1.18.6 active 1 kubernetes-master jujucharms 850 ubuntu exposed kubernetes-worker 1.18.6 active 1 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*activeidle 0/lxd/0 10.123.107.225 Certificate Authority connected. etcd/0* activeidle 010.70.13.93 2379/tcp Healthy with 1 known peer kubernetes-master/0* activeidle 010.70.13.93 6443/tcp Kubernetes master running. containerd/1activeidle10.70.13.93 Container runtime available flannel/1 activeidle10.70.13.93 Flannel subnet 10.1.67.1/24 kubernetes-worker/0* activeidle 110.70.13.16880/tcp,443/tcp Kubernetes worker running. containerd/0* activeidle10.70.13.168 Container runtime available flannel/0* activeidle10.70.13.168 Flannel subnet 10.1.99.1/24 Machine StateDNS Inst id Series AZ Message 0started 10.70.13.93 juju-62238e-0bionic Running 0/lxd/0 started 10.123.107.225 juju-62238e-0-lxd-0 bionic Container started 1started 10.70.13.168juju-62238e-1bionic Running # kubectl get nodes NAMESTATUS ROLESAGE VERSION juju-62238e-1 Ready 74m v1.18.6 Output about pods on the cluster # kubectl get pods No resources found in default namespace. root@m8360041:~# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE ingress-nginx-kubernetes-worker default-http-backend-kubernetes-worker-6fc4c9975-2dwsc 1/1 Running 0 41m ingress-nginx-kubernetes-worker nginx-ingress-controller-kubernetes-worker-qmz2j 1/1 Running 0 41m kube-system coredns-7f748b899d-dc5hx 1/1 Running0 42m kube-system kube-state-metrics-69f474f8cb-9s85h 0/1 CrashLoopBackOff 26 42m kube-system metrics-server-v0.3.6-5c9f85bbd6-8mksp 2/2 Running0 42m kubernetes-dashboard dashboard-metrics-scraper-78d587b6b-2ggmz 0/1 CrashLoopBackOff 26 42m kubernetes-dashboard kubernetes-dashboard-76b6648555-x4fng 1/1 Running0 42m ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187023 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-187023 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889763 Title: [UBUNTU 20.04] kubernetes-core is not fully installed on s390x Status in linux package in Ubuntu: New Bug description: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Expected result - 1 master and 1 worker node. Actual result - just 1 node. # juju status Model Controller Cloud/Region Version SLA
[Kernel-packages] [Bug 1889763] [NEW] [UBUNTU 20.04] kubernetes-core is not fully installed on s390x
You have been subscribed to a public bug: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Expected result - 1 master and 1 worker node. Actual result - just 1 node. # juju status Model Controller Cloud/Region Version SLA Timestamp k8slocalhost-localhost localhost/localhost 2.8.1unsupported 11:28:37+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3active 2 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsajujucharms 318 ubuntu etcd 3.3.19 active 1 etcd jujucharms 521 ubuntu flannel0.11.0 active 2 flanneljujucharms 492 ubuntu kubernetes-master 1.18.6 active 1 kubernetes-master jujucharms 850 ubuntu exposed kubernetes-worker 1.18.6 active 1 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*activeidle 0/lxd/0 10.123.107.225 Certificate Authority connected. etcd/0* activeidle 010.70.13.93 2379/tcp Healthy with 1 known peer kubernetes-master/0* activeidle 010.70.13.93 6443/tcp Kubernetes master running. containerd/1activeidle10.70.13.93 Container runtime available flannel/1 activeidle10.70.13.93 Flannel subnet 10.1.67.1/24 kubernetes-worker/0* activeidle 110.70.13.16880/tcp,443/tcp Kubernetes worker running. containerd/0* activeidle10.70.13.168 Container runtime available flannel/0* activeidle10.70.13.168 Flannel subnet 10.1.99.1/24 Machine StateDNS Inst id Series AZ Message 0started 10.70.13.93 juju-62238e-0bionic Running 0/lxd/0 started 10.123.107.225 juju-62238e-0-lxd-0 bionic Container started 1started 10.70.13.168juju-62238e-1bionic Running # kubectl get nodes NAMESTATUS ROLESAGE VERSION juju-62238e-1 Ready 74m v1.18.6 Output about pods on the cluster # kubectl get pods No resources found in default namespace. root@m8360041:~# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE ingress-nginx-kubernetes-worker default-http-backend-kubernetes-worker-6fc4c9975-2dwsc 1/1 Running 0 41m ingress-nginx-kubernetes-worker nginx-ingress-controller-kubernetes-worker-qmz2j 1/1 Running 0 41m kube-system coredns-7f748b899d-dc5hx 1/1 Running0 42m kube-system kube-state-metrics-69f474f8cb-9s85h 0/1 CrashLoopBackOff 26 42m kube-system metrics-server-v0.3.6-5c9f85bbd6-8mksp 2/2 Running0 42m kubernetes-dashboard dashboard-metrics-scraper-78d587b6b-2ggmz 0/1 CrashLoopBackOff 26 42m kubernetes-dashboard kubernetes-dashboard-76b6648555-x4fng 1/1 Running0 42m ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187023 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] kubernetes-core is not fully installed on s390x https://bugs.launchpad.net/bugs/1889763 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 1889761] [NEW] [UBUNTU 20.04] nfs storage failed to run on top of kubernetes-core cluster on s390x
Public bug reported: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Install nfs as it is mentioned at https://ubuntu.com/kubernetes/docs/storage juju deploy nfs --constraints root-disk=10G juju add-relation nfs kubernetes-worker Expected result: `kubectl get sc,po` will show running pod and storage class Actual result: # kubectl get sc,po NAMEPROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE storageclass.storage.k8s.io/default (default) fuseim.pri/ifs Delete Immediate false 2m17s NAME READY STATUS RESTARTS AGE pod/nfs-client-provisioner-7698b8dbc9-wj56n 0/1 ContainerCreating 0 2m17s # kubectl describe pod nfs-client-provisioner-7698b8dbc9-wj56n Name: nfs-client-provisioner-7698b8dbc9-wj56n Namespace: default Priority: 0 Node: juju-62238e-2/10.70.13.80 Start Time: Fri, 31 Jul 2020 11:39:19 +0200 Labels: app=nfs-client-provisioner pod-template-hash=7698b8dbc9 Annotations: Status: Pending IP: IPs: Controlled By: ReplicaSet/nfs-client-provisioner-7698b8dbc9 Containers: nfs-client-provisioner: Container ID: Image: rocks.canonical.com:443/cdk/external_storage/nfs-client-provisioner:v3.1.0-k8s1.11 Image ID: Port: Host Port: State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Environment: PROVISIONER_NAME: fuseim.pri/ifs NFS_SERVER:10.70.13.33 NFS_PATH: /srv/data/kubernetes-worker Mounts: /persistentvolumes from nfs-client-root (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-r2qgb (ro) Conditions: Type Status Initialized True Ready False ContainersReady False PodScheduled True Volumes: nfs-client-root: Type: NFS (an NFS mount that lasts the lifetime of a pod) Server:10.70.13.33 Path: /srv/data/kubernetes-worker ReadOnly: false default-token-r2qgb: Type:Secret (a volume populated by a Secret) SecretName: default-token-r2qgb Optional:false QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason AgeFromMessage -- --- Normal Scheduled default-scheduler Successfully assigned default/nfs-client-provisioner-7698b8dbc9-wj56n to juju-62238e-2 Warning FailedMount 2m58s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root --scope -- mount -t nfs 10.70.13.33:/srv/data/kubernetes-worker /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root Output: Running scope as unit: run-r946191ed443941e5ad6dcc42ede13325.scope mount.nfs: requested NFS version or transport protocol is not supported Warning FailedMount 2m57s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root --scope -- mount -t nfs 10.70.13.33:/srv/data/kubernetes-worker /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root Output: Running scope as unit: run-r5291c4d534b54caa9a2a508e128f00af.scope mount.nfs: requested NFS version or transport protocol is not supported Warning FailedMount 2m56s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 So nfs pod actually fails to start because of "requested NFS version or transport protocol is not supported" ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187024 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-187024 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners
[Kernel-packages] [Bug 1889761] [NEW] [UBUNTU 20.04] nfs storage failed to run on top of kubernetes-core cluster on s390x
You have been subscribed to a public bug: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Install nfs as it is mentioned at https://ubuntu.com/kubernetes/docs/storage juju deploy nfs --constraints root-disk=10G juju add-relation nfs kubernetes-worker Expected result: `kubectl get sc,po` will show running pod and storage class Actual result: # kubectl get sc,po NAMEPROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE storageclass.storage.k8s.io/default (default) fuseim.pri/ifs Delete Immediate false 2m17s NAME READY STATUS RESTARTS AGE pod/nfs-client-provisioner-7698b8dbc9-wj56n 0/1 ContainerCreating 0 2m17s # kubectl describe pod nfs-client-provisioner-7698b8dbc9-wj56n Name: nfs-client-provisioner-7698b8dbc9-wj56n Namespace: default Priority: 0 Node: juju-62238e-2/10.70.13.80 Start Time: Fri, 31 Jul 2020 11:39:19 +0200 Labels: app=nfs-client-provisioner pod-template-hash=7698b8dbc9 Annotations: Status: Pending IP: IPs: Controlled By: ReplicaSet/nfs-client-provisioner-7698b8dbc9 Containers: nfs-client-provisioner: Container ID: Image: rocks.canonical.com:443/cdk/external_storage/nfs-client-provisioner:v3.1.0-k8s1.11 Image ID: Port: Host Port: State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Environment: PROVISIONER_NAME: fuseim.pri/ifs NFS_SERVER:10.70.13.33 NFS_PATH: /srv/data/kubernetes-worker Mounts: /persistentvolumes from nfs-client-root (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-r2qgb (ro) Conditions: Type Status Initialized True Ready False ContainersReady False PodScheduled True Volumes: nfs-client-root: Type: NFS (an NFS mount that lasts the lifetime of a pod) Server:10.70.13.33 Path: /srv/data/kubernetes-worker ReadOnly: false default-token-r2qgb: Type:Secret (a volume populated by a Secret) SecretName: default-token-r2qgb Optional:false QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason AgeFromMessage -- --- Normal Scheduled default-scheduler Successfully assigned default/nfs-client-provisioner-7698b8dbc9-wj56n to juju-62238e-2 Warning FailedMount 2m58s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root --scope -- mount -t nfs 10.70.13.33:/srv/data/kubernetes-worker /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root Output: Running scope as unit: run-r946191ed443941e5ad6dcc42ede13325.scope mount.nfs: requested NFS version or transport protocol is not supported Warning FailedMount 2m57s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 Mounting command: systemd-run Mounting arguments: --description=Kubernetes transient mount for /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root --scope -- mount -t nfs 10.70.13.33:/srv/data/kubernetes-worker /var/lib/kubelet/pods/98db0283-95db-47fc-911e-e4375fd9f6cf/volumes/kubernetes.io~nfs/nfs-client-root Output: Running scope as unit: run-r5291c4d534b54caa9a2a508e128f00af.scope mount.nfs: requested NFS version or transport protocol is not supported Warning FailedMount 2m56s kubelet, juju-62238e-2 MountVolume.SetUp failed for volume "nfs-client-root" : mount failed: exit status 32 So nfs pod actually fails to start because of "requested NFS version or transport protocol is not supported" ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187024 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] nfs storage failed to run on top of kubernetes-core cluster on s390x https://bugs.launchpad.net/bugs/1889761 You received this bug
[Kernel-packages] [Bug 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM
Oh Sorry Frank, I misread the bug title, I thought this was for KVM kernel. For s390x KVM, the test has been blocked by the MAAS issue, I will change the status back to confirmed and keep an eye on this when we can test it again. Thanks ** Changed in: ubuntu-z-systems Status: Fix Released => Confirmed ** Changed in: ubuntu-kernel-tests Status: Fix Released => 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/1809639 Title: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: Confirmed Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4 tests failed: [11] ftrace - function glob filters [FAIL] [23] Kprobe event argument syntax [FAIL] [36] event trigger - test histogram trigger [FAIL] [51] (instance) event trigger - test histogram trigger [FAIL] With the test suite in the upstream kernel tree, 3 of these failures can be reproduced, except this one: -e -n [34] Kprobe event argument syntax -e[UNTESTED] $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' TAP version 13 selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] event tracing - enable/disable with event level files [PASS] [6] event tracing - restricts events based on pid [PASS] [7] event tracing - enable/disable with subsystem level files [PASS] [8] event tracing - enable/disable with top level files [PASS] [9] ftrace - function graph filters with stack tracer [PASS] [10] ftrace - function graph filters [PASS] [11] ftrace - function glob filters [FAIL] [12] ftrace - function pid filters[PASS] [13] ftrace - test for function event triggers[PASS] [14] ftrace - function profiler with function tracing [PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances[PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument[UNTESTED] [23] Kprobe event argument syntax [FAIL] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer[PASS] [27] Kprobe dynamic event - probing module[PASS] [28] Kretprobe dynamic event with arguments [PASS] [29] Kretprobe dynamic event with maxactive [PASS] [30] Register/unregister many kprobe events [PASS] [31] Kprobe events - probe points [PASS] [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED] [33] event trigger - test event enable/disable trigger[PASS] [34] event trigger - test trigger filter [PASS] [35] event trigger - test histogram modifiers [PASS] [36] event trigger - test histogram trigger [FAIL] [37] event trigger - test multiple histogram triggers [PASS] [38] event trigger - test snapshot-trigger[PASS] [39] event trigger - test stacktrace-trigger [PASS] [40] event trigger - test traceon/off trigger [PASS] [41] (instance) Basic test for tracers [PASS] [42] (instance) Basic trace clock test [PASS] [43] (instance) event tracing - enable/disable with event level files [PASS] [44] (instance) event tracing - restricts events based on pid[PASS] [45] (instance) event tracing - enable/disable with subsystem level files [PASS] [46] (instance) ftrace - test for function event triggers[PASS] [47] (instance) ftrace - test for function traceon/off triggers [PASS] [48] (instance) event trigger - test event enable/disable trigger[PASS] [49] (instance) event trigger - test trigger filter [PASS] [50] (instance) event trigger - test histogram modifiers [PASS] [51] (instance) event trigger - test histogram trigger [FAIL] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 46
[Kernel-packages] [Bug 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems 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/1809639 Title: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4 tests failed: [11] ftrace - function glob filters [FAIL] [23] Kprobe event argument syntax [FAIL] [36] event trigger - test histogram trigger [FAIL] [51] (instance) event trigger - test histogram trigger [FAIL] With the test suite in the upstream kernel tree, 3 of these failures can be reproduced, except this one: -e -n [34] Kprobe event argument syntax -e[UNTESTED] $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' TAP version 13 selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] event tracing - enable/disable with event level files [PASS] [6] event tracing - restricts events based on pid [PASS] [7] event tracing - enable/disable with subsystem level files [PASS] [8] event tracing - enable/disable with top level files [PASS] [9] ftrace - function graph filters with stack tracer [PASS] [10] ftrace - function graph filters [PASS] [11] ftrace - function glob filters [FAIL] [12] ftrace - function pid filters[PASS] [13] ftrace - test for function event triggers[PASS] [14] ftrace - function profiler with function tracing [PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances[PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument[UNTESTED] [23] Kprobe event argument syntax [FAIL] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer[PASS] [27] Kprobe dynamic event - probing module[PASS] [28] Kretprobe dynamic event with arguments [PASS] [29] Kretprobe dynamic event with maxactive [PASS] [30] Register/unregister many kprobe events [PASS] [31] Kprobe events - probe points [PASS] [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED] [33] event trigger - test event enable/disable trigger[PASS] [34] event trigger - test trigger filter [PASS] [35] event trigger - test histogram modifiers [PASS] [36] event trigger - test histogram trigger [FAIL] [37] event trigger - test multiple histogram triggers [PASS] [38] event trigger - test snapshot-trigger[PASS] [39] event trigger - test stacktrace-trigger [PASS] [40] event trigger - test traceon/off trigger [PASS] [41] (instance) Basic test for tracers [PASS] [42] (instance) Basic trace clock test [PASS] [43] (instance) event tracing - enable/disable with event level files [PASS] [44] (instance) event tracing - restricts events based on pid[PASS] [45] (instance) event tracing - enable/disable with subsystem level files [PASS] [46] (instance) ftrace - test for function event triggers[PASS] [47] (instance) ftrace - test for function traceon/off triggers [PASS] [48] (instance) event trigger - test event enable/disable trigger[PASS] [49] (instance) event trigger - test trigger filter [PASS] [50] (instance) event trigger - test histogram modifiers [PASS] [51] (instance) event trigger - test histogram trigger [FAIL] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 46 # of failed: 4 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 not ok 1..1 selftests: ftracetest [FAIL] make[1]: Leaving directory
[Kernel-packages] [Bug 1889375] Re: Fix right speaker of HP laptop
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1889375 Title: Fix right speaker of HP laptop Status in HWE Next: New 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: [Impact] Right speaker on an HP laptop doesn't work. [Fix] Correctly enable the AMP to drive the right speaker. [Test] Open Gnome Control Center to test the right channel. I can hear the "front right" voice from the right speaker. [Regression Potential] Low. It's only affect a platform which is not on the market yet. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1889375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
That#s a spin off of the already Fix Released ticket LP 1888654 ** Package changed: linux (Ubuntu) => binutils (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: binutils (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Also affects: binutils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: binutils (Ubuntu Groovy) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Changed in: binutils (Ubuntu Groovy) Status: New => Fix Released ** Changed in: binutils (Ubuntu Groovy) Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) ** Changed in: binutils (Ubuntu Focal) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- 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/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: New Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889740] Re: [UBUNTU 20.04] Charmed kubernetes is not installed because etcd part is not running
** Package changed: linux (Ubuntu) => etcd-snaps ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: etcd-snaps Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Changed in: ubuntu-z-systems Importance: Undecided => High -- 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/1889740 Title: [UBUNTU 20.04] Charmed kubernetes is not installed because etcd part is not running Status in Etcd Snaps: New Status in Ubuntu on IBM z Systems: New Bug description: Steps to reproduce: Clean Z LPAR machine. Ubuntu 18.04.4 is inatalled. Followed official documentation to install Charmed Kubernetes https://ubuntu.com/kubernetes/docs/install-local. Actual results: Cluster did not start and hang in the follow state: # juju status Model Controller Cloud/Region Version SLA Timestamp k8slocalhost-localhost localhost/localhost 2.8.1unsupported 09:43:44+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3active 5 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.19 waiting 3 etcd jujucharms 521 ubuntu flannel0.11.0 waiting 5 flannel jujucharms 492 ubuntu kubeapi-load-balancer 1.14.0 active 1 kubeapi-load-balancer jujucharms 730 ubuntu exposed kubernetes-master 1.18.6 waiting 2 kubernetes-master jujucharms 850 ubuntu kubernetes-worker 1.18.6 waiting 3 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*active idle 010.70.13.64 Certificate Authority connected. etcd/0* active idle 110.70.13.173 2379/tcp Errored with 0 known peers etcd/1active idle 210.70.13.127 2379/tcp Errored with 0 known peers etcd/2waiting idle 310.70.13.82 Waiting to retry etcd registration kubeapi-load-balancer/0* active idle 410.70.13.32 443/tcp Loadbalancer ready. kubernetes-master/0 waiting executing 510.70.13.77 (leader-settings-changed) Waiting for kube-api-endpoint relation containerd/3active idle10.70.13.77 Container runtime available flannel/3 maintenance executing 10.70.13.77 Negotiating flannel network subnet. kubernetes-master/1* waiting executing 610.70.13.95 Waiting for CNI plugins to become available containerd/4active idle10.70.13.95 Container runtime available flannel/4 maintenance idle10.70.13.95 Negotiating flannel network subnet. kubernetes-worker/0 waiting idle 710.70.13.34 Waiting for cluster DNS. containerd/0* active idle10.70.13.34 Container runtime available flannel/0* waiting idle10.70.13.34 Waiting on etcd. kubernetes-worker/1* waiting executing 810.70.13.204 Waiting for cluster DNS. containerd/1active idle10.70.13.204 Container runtime available flannel/1 maintenance executing 10.70.13.204 Negotiating flannel network subnet. kubernetes-worker/2 waiting idle 910.70.13.25 Waiting for cluster DNS. containerd/2active idle10.70.13.25 Container runtime available flannel/2 maintenance idle10.70.13.25 Negotiating flannel network subnet. syslog from one of the etcd nodes is attached To manage notifications about this bug go to: https://bugs.launchpad.net/etcd-snaps/+bug/1889740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886908] Re: Add support for Atlantic NIC firmware v4
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1886908 Title: Add support for Atlantic NIC firmware v4 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Atlantic NIC doesn't work. [Fix] Add firmware v4 support. [Test] With the patch applied, the driver probe success. Using iperf as a smoketest shows positive result. [Regression Potential] None. We were contacted by Marvell after I sent the patch to upstream, and they told us firmware v4 is created specifically for this upcoming platform. There are none firmware v4 in production. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889742] [NEW] [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
Public bug reported: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187207 severity-medium targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-187207 severity-medium targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889742] [NEW] [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
You have been subscribed to a public bug: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187207 severity-medium targetmilestone-inin2004 -- [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) https://bugs.launchpad.net/bugs/1889742 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 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM
This is not failing anymore on KVM kernels. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809639 Title: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: 4 tests failed: [11] ftrace - function glob filters [FAIL] [23] Kprobe event argument syntax [FAIL] [36] event trigger - test histogram trigger [FAIL] [51] (instance) event trigger - test histogram trigger [FAIL] With the test suite in the upstream kernel tree, 3 of these failures can be reproduced, except this one: -e -n [34] Kprobe event argument syntax -e[UNTESTED] $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' make[1]: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests/ftrace' TAP version 13 selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] event tracing - enable/disable with event level files [PASS] [6] event tracing - restricts events based on pid [PASS] [7] event tracing - enable/disable with subsystem level files [PASS] [8] event tracing - enable/disable with top level files [PASS] [9] ftrace - function graph filters with stack tracer [PASS] [10] ftrace - function graph filters [PASS] [11] ftrace - function glob filters [FAIL] [12] ftrace - function pid filters[PASS] [13] ftrace - test for function event triggers[PASS] [14] ftrace - function profiler with function tracing [PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances[PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument[UNTESTED] [23] Kprobe event argument syntax [FAIL] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer[PASS] [27] Kprobe dynamic event - probing module[PASS] [28] Kretprobe dynamic event with arguments [PASS] [29] Kretprobe dynamic event with maxactive [PASS] [30] Register/unregister many kprobe events [PASS] [31] Kprobe events - probe points [PASS] [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED] [33] event trigger - test event enable/disable trigger[PASS] [34] event trigger - test trigger filter [PASS] [35] event trigger - test histogram modifiers [PASS] [36] event trigger - test histogram trigger [FAIL] [37] event trigger - test multiple histogram triggers [PASS] [38] event trigger - test snapshot-trigger[PASS] [39] event trigger - test stacktrace-trigger [PASS] [40] event trigger - test traceon/off trigger [PASS] [41] (instance) Basic test for tracers [PASS] [42] (instance) Basic trace clock test [PASS] [43] (instance) event tracing - enable/disable with event level files [PASS] [44] (instance) event tracing - restricts events based on pid[PASS] [45] (instance) event tracing - enable/disable with subsystem level files [PASS] [46] (instance) ftrace - test for function event triggers[PASS] [47] (instance) ftrace - test for function traceon/off triggers [PASS] [48] (instance) event trigger - test event enable/disable trigger[PASS] [49] (instance) event trigger - test trigger filter [PASS] [50] (instance) event trigger - test histogram modifiers [PASS] [51] (instance) event trigger - test histogram trigger [FAIL] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 46 # of failed: 4 # of unresolved: 0 # of untested: 1 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 not ok 1..1 selftests: ftracetest [FAIL]
[Kernel-packages] [Bug 1812318] Re: ftrace test in ubuntu_kernel_selftests failed on KVM kernels
For the test itself, this can be fixed with https://github.com/torvalds/linux/commit/cbd965bde74c3d0e53798404fd4b9829a68ccec8 #diff-71290e3874c89695bb4bc63f892d5c93 -- 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/1812318 Title: ftrace test in ubuntu_kernel_selftests failed on KVM kernels Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Bionic: Fix Released Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Fix Released Bug description: This test failed with: Error: No ftrace directory found In the script: DEBUGFS_DIR=`grep debugfs /proc/mounts | cut -f2 -d' ' | head -1` if [ -z "$DEBUGFS_DIR" ]; then TRACING_DIR=`grep tracefs /proc/mounts | cut -f2 -d' ' | head -1` else TRACING_DIR=$DEBUGFS_DIR/tracing fi The script exit here: # Verify parameters if [ -z "$TRACING_DIR" -o ! -d "$TRACING_DIR" ]; then errexit "No ftrace directory found" fi DEBUGFS_DIR=/sys/kernel/debug TRACING_DIR=/sys/kernel/debug/tracing ls: cannot access '/sys/kernel/debug/tracing': No such file or directory 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: Fri Jan 18 03:04:17 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/1812318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889740] syslog from etcd node
Default Comment by Bridge ** Attachment added: "syslog from etcd node" https://bugs.launchpad.net/bugs/1889740/+attachment/5397356/+files/etcd_syslog ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889740 Title: [UBUNTU 20.04] Charmed kubernetes is not installed because etcd part is not running Status in linux package in Ubuntu: New Bug description: Steps to reproduce: Clean Z LPAR machine. Ubuntu 18.04.4 is inatalled. Followed official documentation to install Charmed Kubernetes https://ubuntu.com/kubernetes/docs/install-local. Actual results: Cluster did not start and hang in the follow state: # juju status Model Controller Cloud/Region Version SLA Timestamp k8slocalhost-localhost localhost/localhost 2.8.1unsupported 09:43:44+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3active 5 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.19 waiting 3 etcd jujucharms 521 ubuntu flannel0.11.0 waiting 5 flannel jujucharms 492 ubuntu kubeapi-load-balancer 1.14.0 active 1 kubeapi-load-balancer jujucharms 730 ubuntu exposed kubernetes-master 1.18.6 waiting 2 kubernetes-master jujucharms 850 ubuntu kubernetes-worker 1.18.6 waiting 3 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*active idle 010.70.13.64 Certificate Authority connected. etcd/0* active idle 110.70.13.173 2379/tcp Errored with 0 known peers etcd/1active idle 210.70.13.127 2379/tcp Errored with 0 known peers etcd/2waiting idle 310.70.13.82 Waiting to retry etcd registration kubeapi-load-balancer/0* active idle 410.70.13.32 443/tcp Loadbalancer ready. kubernetes-master/0 waiting executing 510.70.13.77 (leader-settings-changed) Waiting for kube-api-endpoint relation containerd/3active idle10.70.13.77 Container runtime available flannel/3 maintenance executing 10.70.13.77 Negotiating flannel network subnet. kubernetes-master/1* waiting executing 610.70.13.95 Waiting for CNI plugins to become available containerd/4active idle10.70.13.95 Container runtime available flannel/4 maintenance idle10.70.13.95 Negotiating flannel network subnet. kubernetes-worker/0 waiting idle 710.70.13.34 Waiting for cluster DNS. containerd/0* active idle10.70.13.34 Container runtime available flannel/0* waiting idle10.70.13.34 Waiting on etcd. kubernetes-worker/1* waiting executing 810.70.13.204 Waiting for cluster DNS. containerd/1active idle10.70.13.204 Container runtime available flannel/1 maintenance executing 10.70.13.204 Negotiating flannel network subnet. kubernetes-worker/2 waiting idle 910.70.13.25 Waiting for cluster DNS. containerd/2active idle10.70.13.25 Container runtime available flannel/2 maintenance idle10.70.13.25 Negotiating flannel network subnet. syslog from one of the etcd nodes is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889740] [NEW] [UBUNTU 20.04] Charmed kubernetes is not installed because etcd part is not running
You have been subscribed to a public bug: Steps to reproduce: Clean Z LPAR machine. Ubuntu 18.04.4 is inatalled. Followed official documentation to install Charmed Kubernetes https://ubuntu.com/kubernetes/docs/install-local. Actual results: Cluster did not start and hang in the follow state: # juju status Model Controller Cloud/Region Version SLA Timestamp k8slocalhost-localhost localhost/localhost 2.8.1unsupported 09:43:44+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3active 5 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.19 waiting 3 etcd jujucharms 521 ubuntu flannel0.11.0 waiting 5 flannel jujucharms 492 ubuntu kubeapi-load-balancer 1.14.0 active 1 kubeapi-load-balancer jujucharms 730 ubuntu exposed kubernetes-master 1.18.6 waiting 2 kubernetes-master jujucharms 850 ubuntu kubernetes-worker 1.18.6 waiting 3 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*active idle 010.70.13.64 Certificate Authority connected. etcd/0* active idle 110.70.13.173 2379/tcp Errored with 0 known peers etcd/1active idle 210.70.13.127 2379/tcp Errored with 0 known peers etcd/2waiting idle 310.70.13.82 Waiting to retry etcd registration kubeapi-load-balancer/0* active idle 410.70.13.32 443/tcp Loadbalancer ready. kubernetes-master/0 waiting executing 510.70.13.77 (leader-settings-changed) Waiting for kube-api-endpoint relation containerd/3active idle10.70.13.77 Container runtime available flannel/3 maintenance executing 10.70.13.77 Negotiating flannel network subnet. kubernetes-master/1* waiting executing 610.70.13.95 Waiting for CNI plugins to become available containerd/4active idle10.70.13.95 Container runtime available flannel/4 maintenance idle10.70.13.95 Negotiating flannel network subnet. kubernetes-worker/0 waiting idle 710.70.13.34 Waiting for cluster DNS. containerd/0* active idle10.70.13.34 Container runtime available flannel/0* waiting idle10.70.13.34 Waiting on etcd. kubernetes-worker/1* waiting executing 810.70.13.204 Waiting for cluster DNS. containerd/1active idle10.70.13.204 Container runtime available flannel/1 maintenance executing 10.70.13.204 Negotiating flannel network subnet. kubernetes-worker/2 waiting idle 910.70.13.25 Waiting for cluster DNS. containerd/2active idle10.70.13.25 Container runtime available flannel/2 maintenance idle10.70.13.25 Negotiating flannel network subnet. syslog from one of the etcd nodes is attached ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187022 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] Charmed kubernetes is not installed because etcd part is not running https://bugs.launchpad.net/bugs/1889740 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 1889735] Re: tap: use after free
** Description changed: - TBD + [Impact] + + If the socket buffer array of a tap queue is full, a received package + needs to be dropped. Currently, the check for the array being full is + performed lockless, which might lead to use-after-free errors if the + socket buffer array has been resized. + + [Test Case] + + TBD. + + [Regression Potential] + + The check for the array being full is simply dropped. In case the array + is full, subsequent frame handling will fail and the frame is eventually + dropped. A regression would manifest itself if the frame is not dropped + for whatever reason and inserted into the (ring) buffer, overwriting the + oldest frame in the buffer. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) 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/1889735 Title: tap: use after free Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: [Impact] If the socket buffer array of a tap queue is full, a received package needs to be dropped. Currently, the check for the array being full is performed lockless, which might lead to use-after-free errors if the socket buffer array has been resized. [Test Case] TBD. [Regression Potential] The check for the array being full is simply dropped. In case the array is full, subsequent frame handling will fail and the frame is eventually dropped. A regression would manifest itself if the frame is not dropped for whatever reason and inserted into the (ring) buffer, overwriting the oldest frame in the buffer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887734] Re: soc/amd/renoir: detect dmic from acpi table
Tested on an AMD renoir machine,the dmic was detected from ACPI table. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887734 Title: soc/amd/renoir: detect dmic from acpi table Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: Groovy kernel already merged the patchset [Impact] On the amd renoir machines, there is possibility that they have no dmic from the hardware desgin, but the driver register a dmic unconditionally, to avoid it, add the dmic detection code in the driver. [Fix] Backport 3 patches from upstream. [Test Case] On the 3 Lenovo ADM renoir machines, boot the kernel with this patchset, all dmic could be detected and registered as before. Disable the dmic in the BIOS, the driver can't detect the dmic and the dmic is not registered in the driver. [Regression Risk] Low, this SRU are only specific to soc/amd/renoir, and we already tested on 3 lenovo machines, they worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888166] Re: soc/amd/renoir: change the module name to make it work with ucm3
Checked the module name, it is changed. and could be loaded on the machine. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1888166 Title: soc/amd/renoir: change the module name to make it work with ucm3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] the alsa upstream worte the ucm3 files for amd renoir audio, but to load the ucm3, it depends on the kernel module name, and the upstream ucm3 needs the name snd-xxx, so we need to backport the patch from mainline kernel to change the kernel module name to meet ucm3 requirement. [Fix] Backport 1 patch from upstream. [Test Case] boot the kernel with the patch on amd renoir machines (lenovo machines), the audio driver works well (via command line like aplay or areord), then upgrade the alsa-lib and alsa-ucm-conf to 1.2.3.2, now we could see the audio devices from gnome, and they work well. [Regression Risk] Low, this SRU are only specific to soc/amd/renoir, and we already tested on 2 lenovo machines, their audio worked as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1888166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] Got below error message after upgraded Focal kernel(v5.4) [ 576.793852] blk_update_request: operation not supported error, dev nvme1n1, sector 4218887 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 This issue was introduced by below commit which added write zeros command 6e02318eaea5 nvme: add support for the Write Zeroes command SK hynix firmware has a bug that it treats NLB as max value instead of a range, so the NLB passed isn't a valid value to the firmware. [Fix] Add a quirk to disable write zeros support [Test] Verified on the machine with SK hynix PC400 nvme machine. [Regression Potential] Low, it's a quirk to a specific PCI ID. == Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: Precision dmi.product.name: Precision 3930 Rack dmi.product.sku: 0873 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1872383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1889735] [NEW] tap: use after free
Public bug reported: TBD ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Bionic) 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/1889735 Title: tap: use after free Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889735] 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 1889735 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 Bionic) 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/1889735 Title: tap: use after free Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886785] Re: [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1886785 Title: [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue. Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Incomplete Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] On AMD RENOIR gpu, after S3 backlight brightness can not be changed. [Fix] Pevious patch prevent loading iram, then dmcu can not work. Remove unused check to load iram right. Then backlight works well. [Test] Verified on hardware, after 10 times of S3, backlight can be changed by hotkey. [Regression Potential] Low Upstream fix, backports is minimal. RENOIR is only supported on oem-5.6, no focal patch. Harry Wentland (1): Revert "drm/amd/display: disable dcn20 abm feature for bring up" drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] Got below error message after upgraded Focal kernel(v5.4) [ 576.793852] blk_update_request: operation not supported error, dev nvme1n1, sector 4218887 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 This issue was introduced by below commit which added write zeros command 6e02318eaea5 nvme: add support for the Write Zeroes command SK hynix firmware has a bug that it treats NLB as max value instead of a range, so the NLB passed isn't a valid value to the firmware. [Fix] Add a quirk to disable write zeros support [Test] Verified on the machine with SK hynix PC400 nvme machine. [Regression Potential] Low, it's a quirk to a specific PCI ID. == Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020
[Kernel-packages] [Bug 1886744] Re: Enable Quectel EG95 LTE modem [2c7c:0195]
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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: Fix Committed Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed 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 1880519] Re: System stops responding while entering S3 with SD card installed
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-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: Fix Committed 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: Fix Committed 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,
[Kernel-packages] [Bug 1886860] Re: cgroup refcount is bogus when cgroup_sk_alloc is disabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1886860 Title: cgroup refcount is bogus when cgroup_sk_alloc is disabled Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux source package in Eoan: In Progress Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: New Bug description: [Impact] When net_prio and net_cls cgroups are used, cgroup refcount is bogus, as it's not incremented anymore, but decremented when sockets are closed. This might lead to crashes possibly because of use-after-free when packets are received as shown in LP #1886668. [Test case] Ran reproducer from comment #2. [Regression potential] We could break the use of cgroup bpf. The use of cgroup bpf looks to still be working from the reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887904] Re: Random reboots
** 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/1887904 Title: Random reboots Status in linux package in Ubuntu: Fix Released Bug description: While using the system (Ubuntu 20.04) the system reboots with no apparent cause. Never happened without using keyboard and/or mouse (e.g., doesn't happen at night). Sometimes happens while just touching the mouse, but sometimes after 30 minutes of extensive use. I built a custom kernel per these instructions: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild and the problem does not happen so far (over a day of work where before it happened at least every hour) 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/controlC1: yakov 1952 F pulseaudio /dev/snd/controlC0: yakov 1952 F pulseaudio /dev/snd/controlC2: yakov 1952 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 10:40:52 2020 InstallationDate: Installed on 2019-10-21 (270 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=/dev/mapper/vg0-ubuntu--20.04 ro quiet splash nvidia-drm.modeset=1 debug ignore_loglevel 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-19 (27 days ago) dmi.bios.date: 10/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2606 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-H GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2606:bd10/24/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-HGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL 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/1887904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887734] Re: soc/amd/renoir: detect dmic from acpi table
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887734 Title: soc/amd/renoir: detect dmic from acpi table Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: Groovy kernel already merged the patchset [Impact] On the amd renoir machines, there is possibility that they have no dmic from the hardware desgin, but the driver register a dmic unconditionally, to avoid it, add the dmic detection code in the driver. [Fix] Backport 3 patches from upstream. [Test Case] On the 3 Lenovo ADM renoir machines, boot the kernel with this patchset, all dmic could be detected and registered as before. Disable the dmic in the BIOS, the driver can't detect the dmic and the dmic is not registered in the driver. [Regression Risk] Low, this SRU are only specific to soc/amd/renoir, and we already tested on 3 lenovo machines, they worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886908] Re: Add support for Atlantic NIC firmware v4
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1886908 Title: Add support for Atlantic NIC firmware v4 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Atlantic NIC doesn't work. [Fix] Add firmware v4 support. [Test] With the patch applied, the driver probe success. Using iperf as a smoketest shows positive result. [Regression Potential] None. We were contacted by Marvell after I sent the patch to upstream, and they told us firmware v4 is created specifically for this upcoming platform. There are none firmware v4 in production. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889375] Re: Fix right speaker of HP laptop
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1889375 Title: Fix right speaker of HP laptop Status in HWE Next: New 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: [Impact] Right speaker on an HP laptop doesn't work. [Fix] Correctly enable the AMP to drive the right speaker. [Test] Open Gnome Control Center to test the right channel. I can hear the "front right" voice from the right speaker. [Regression Potential] Low. It's only affect a platform which is not on the market yet. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1889375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888375] Re: Restart the machine successfully after suspend
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1888375 Title: Restart the machine successfully after suspend Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] After suspend then restart, the System would hang during shutdown. [Fix] The commit has pushed to upstream but still wait for the maintainer of IOMMU to apply. https://lore.kernel.org/linux-iommu/20200721001713.24282-1-baolu...@linux.intel.com/ Skip the TE disabling for the quirky gfx dedicated iommu and the system would not hang during shutdown. [test] With the patch, the machine restart successfully. [Regression Potential] low, the patch just skip the TE disabling and wouldn't affect the normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1888375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888166] Re: soc/amd/renoir: change the module name to make it work with ucm3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1888166 Title: soc/amd/renoir: change the module name to make it work with ucm3 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] the alsa upstream worte the ucm3 files for amd renoir audio, but to load the ucm3, it depends on the kernel module name, and the upstream ucm3 needs the name snd-xxx, so we need to backport the patch from mainline kernel to change the kernel module name to meet ucm3 requirement. [Fix] Backport 1 patch from upstream. [Test Case] boot the kernel with the patch on amd renoir machines (lenovo machines), the audio driver works well (via command line like aplay or areord), then upgrade the alsa-lib and alsa-ucm-conf to 1.2.3.2, now we could see the audio devices from gnome, and they work well. [Regression Risk] Low, this SRU are only specific to soc/amd/renoir, and we already tested on 2 lenovo machines, their audio worked as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1888166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888331] Re: Wakeup the system by touching the touchpad
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1888331
Title:
Wakeup the system by touching the touchpad
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Bug description:
[Impact]
Can't wake up by touching the touchpad.
[Fix]
1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
may not want to implement irq_disable callback to lazy disable irq
when client drivers invokes disable_irq(). By overriding irq_disable
callback,
gpiolib ends up always unlazy disabling IRQ.
Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
if irqchip implemented irq_disable. In cases where irq_disable is not
implemented irq_mask is overridden. Similarly override irq_enable callback
only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
also the default behavior on other OSes.
However, if touchpad and touchscreen contact to each other when lid is
closed, wakeup events can be triggered inadventertly.
So let's disable the wakeup by default, but enable the wakeup capability
so users can enable it at their own discretion.
[test]
With the patch and manually enable HID's power/wakeup, the system can wake up
by touching the touchpad.
[Regression Potential]
Low. The two patches are already landed in the upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1888331/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887909] Re: [SRU][F/OEM-5.6] add a new OLED panel support for brightness control
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887909 Title: [SRU][F/OEM-5.6] add a new OLED panel support for brightness control Status in linux package in Ubuntu: Triaged Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] Lenovo reported that a new OLED panel needs dpcd support to change screen brightness. [Fix] Add the panel ID in quirk list to support dpcd control. [Test] Verified on hardware by Lenovo. [Regression Potential] Low Upstream fix, clean cherry-picked. Add an ID only affected on specific hw. Unstable branch already got this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887904] Re: Random reboots
Problem no longer happens with kernel 5.4.0-42-generic. all previous kernels do not have corresponding headers in the repository: *Error! Your kernel headers for kernel 5.4.0-40-generic cannot be found.* so problem cannot be reproduced and can therefore be closd. -- 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/1887904 Title: Random reboots Status in linux package in Ubuntu: Incomplete Bug description: While using the system (Ubuntu 20.04) the system reboots with no apparent cause. Never happened without using keyboard and/or mouse (e.g., doesn't happen at night). Sometimes happens while just touching the mouse, but sometimes after 30 minutes of extensive use. I built a custom kernel per these instructions: https://wiki.ubuntu.com/KernelTeam/GitKernelBuild and the problem does not happen so far (over a day of work where before it happened at least every hour) 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/controlC1: yakov 1952 F pulseaudio /dev/snd/controlC0: yakov 1952 F pulseaudio /dev/snd/controlC2: yakov 1952 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 10:40:52 2020 InstallationDate: Installed on 2019-10-21 (270 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=/dev/mapper/vg0-ubuntu--20.04 ro quiet splash nvidia-drm.modeset=1 debug ignore_loglevel 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-19 (27 days ago) dmi.bios.date: 10/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2606 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-H GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2606:bd10/24/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-HGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL 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/1887904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 Unfortunately, Ubuntu developers forgot something. I have been building my optimized kernel with lz4 for 5 years ... and here it is necessary to compile or upload lz4 and only then e.g. sudo update-initramfs -u -k 5.7.11-ext73-77.11-kabylake-8th and after restarting the message you will not see https://github.com/lz4/lz4 -- 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/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397334/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397333/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397331/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397332/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397330/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397329/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397328/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] Re: xenial/linux: 4.4.0-186.216 - Problem with NFS mount
apport information ** Tags added: apport-collected ** Description changed: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jul 27 05:02 seq + crw-rw 1 root audio 116, 33 Jul 27 05:02 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 + InstallationDate: Installed on 2016-06-02 (1519 days ago) + InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Supermicro Super Server + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi + ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-186-generic N/A + linux-backports-modules-4.4.0-186-generic N/A + linux-firmware 1.157.23 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-186-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 05/23/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2.2 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: X11SSH-LN4F + dmi.board.vendor: Supermicro + dmi.board.version: 1.01 + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 17 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: 0123456789 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: + dmi.product.name: Super Server + dmi.product.version: 0123456789 + dmi.sys.vendor: Supermicro ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397325/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation
[Kernel-packages] [Bug 1889721] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397326/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1889721/+attachment/5397327/+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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Confirmed Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 27 05:02 seq crw-rw 1 root audio 116, 33 Jul 27 05:02 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4bf8bc57-9e9e-4e8b-9bea-6d2b6273d223 InstallationDate: Installed on 2016-06-02 (1519 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server Package: linux (not installed) PciMultimedia: ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-186-generic root=UUID=d355e42f-3b5a-4479-9664-60bcbd373d6b ro net.ifnames=0 nomodeset reboot=acpi ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-186-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSH-LN4F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.2:bd05/23/2018:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSH-LN4F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
@axt thank you for the update. But the problem is my BIOS has now become read only. Earlier last year, I tried to upgrade ubuntu from 17 to 19 and since then the BIOS has become read only. If I make any changes it will not get saved. That's my main issue. I cannot boot from USB, I cannot boot from DVD etc.. My default first boot device is Ubuntu and then windows and then USB and network.. etc.. Even if I do f12 and select boot from USB it doesn't work. @axt I even tried flashing the BIOS it does not boot from my Pen drive. I downloaded the latest version of UEFI as per BIOS Update for Windows 7 (32-bit, 64-bit), Windows 8 (64-bit) , Windows 8.1 (64-bit), Windows10 (64-bit) - Lenovo Z40-70, Z50-70 and tried to execute the package from windows 8 os but after reboot nothing happens. the Bios version is not changed and the bios is still not saving any changes what ever changes I do in it. now I have removed the ubuntu and deleted few partitations of Linux using partition magic. but now the system partition where the UEFI files are there is still there. Last night I tried to run pratation magic. Assigned a drive letter to the system partation then using powershell with admin rights I tried to replace the grubx64.efi.signed in UEFI folder under Ubuntu but it didn't work Now I have removed the Ubuntu folder from that partition and now it directly boots to windows as soon as I start my laptop but my main concern is to fix the BIOS which is not saving my changes in it. -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines:
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
https://thehackernews.com/2020/07/grub2-bootloader- vulnerability.html?fbclid=IwAR0QDfYoo_wLhamrGvv- yO8qIhAi1jlmiYQ92Uw7PwYRCvbJfpHDyoJxcg4 -- 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hello! Would like to let you know that this issue is relevant for me as well. I have ThinkPad 14-IIL, ELAN06034 touchpad is not working. Upgrading the kernel from default 5.4.?? to both 5.6 (linux-oem-20.04) and 5.7.11 (latest available for Ubuntu right now) did not work. Would love to share any other logs/information if required. I also noticed that on kernel 5.7.11 there is a bunch acpi-related errors in dmesg, though I dont think this is relevant. And I also tried decompiling the DSDT and the HID seems to be correct, no or _HID. As far as I know, for IIL there is a separate bug report 1883010, though it is said to be the duplicate of this one, so I am commenting here. -- 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889721] 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 1889721 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- 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/1889721 Title: xenial/linux: 4.4.0-186.216 - Problem with NFS mount Status in linux package in Ubuntu: Incomplete Bug description: Xenial Package: linux-image-generic (4.4.0.186.192) Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a problem with the NFS mounts, when the NFS Server has a timeout. The journal and syslog are reporting thousands of the following messages per second Jul 30 09:05:07 ... kernel: [ 280.904750] xs_tcp_setup_socket: connect returned unhandled error -1 The server becomes instable and OS hungs. Reboot resolves the issue until the next NFS timeout occures. using the previous kernel Linux 4.4.0-185-generic resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
