[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
>From the google_guest_agent code: google_guest_agent/instance_setup.go: func setIOScheduler() error { dir, err := os.Open("/sys/block") if err != nil { return err } defer dir.Close() devs, err := dir.Readdirnames(0) if err != nil { return err } for _, dev := range devs { // Detect if device is using MQ subsystem. stat, err := os.Stat("/sys/block/" + dev + "/mq") if err == nil && stat.IsDir() { f, err := os.OpenFile("/sys/block/"+dev+"/queue/scheduler", os.O_WRONLY|os.O_TRUNC, 0700) if err != nil { return err } _, err = f.Write([]byte("none")) if err != nil { return err } } } return nil } Seems to be intentionally doing that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
This problem is replicated on both virtual and physical machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432934/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
With a modified kernel, I was able to determine the name of the process making the change: google_guest_agent Though I'm not really sure why it is making that change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432935/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Linux 4.15 is a kernel module, and Linux 5.4 is a built-in module. I suspect it's a kernel build option issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432923/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432930/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432931/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432927/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432932/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432933/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432929/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Card0.Codecs.codec97.0.ac97.0-0.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432924/+files/Card0.Codecs.codec97.0.ac97.0-0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432926/+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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432928/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Card0.Codecs.codec97.0.ac97.0-0.regs.txt
apport information ** Attachment added: "Card0.Codecs.codec97.0.ac97.0-0.regs.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432925/+files/Card0.Codecs.codec97.0.ac97.0-0.regs.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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform 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 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
apport information ** Tags added: apport-collected bionic uec-images ** Description changed: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.16 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/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': 'amixer' + Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-11-09 (0 days ago) + InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + MachineType: VMware, Inc. VMware Virtual Platform + 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 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity + ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.173.19 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic uec-images + Uname: Linux 5.4.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lxd plugdev sudo + _MarkForUpload: True + dmi.bios.date: 07/22/2020 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1903612/+attachment/5432922/+files/AlsaDevices.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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$
Re: [Kernel-packages] [Bug 1903467] Re: screen freeze in mid-session
I did consider it. However I read on ubuntu blog that, with DDR drives it is not a good idea bcz it may damage it over time - otherwise ubuntu itself would automatically create such swap partition during installation Meanwhile I try to minimize opening too many apps at same time I still thing the AMDgpu needs to be upgraded to meet the heavy load of latest ubuntu Levi > On Nov 9, 2020, at 22:11, Kai-Heng Feng <1903...@bugs.launchpad.net> wrote: > > One way is to add more swap space and tune swappiness to help the > situation. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1903467 > > Title: > screen freeze in mid-session > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > This is a repeat problem to which I attribute to AMD display driver. The > problem mostly occur using Firefox with 4 or more tabs open. > It's really frustrating to face the prospect of losing data while surfing > the net. > > Thanks > Levi > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: linux-image-5.8.0-26-generic 5.8.0-26.27 > ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 > Uname: Linux 5.8.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu50 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC1: admin-meir 7349 F pulseaudio > /dev/snd/controlC0: admin-meir 7349 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: X-Cinnamon > Date: Sun Nov 8 15:00:55 2020 > InstallationDate: Installed on 2020-09-03 (66 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) > MachineType: Dell Inc. Inspiron 3180 > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcFB: 0 amdgpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic > root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 > RelatedPackageVersions: > linux-restricted-modules-5.8.0-26-generic N/A > linux-backports-modules-5.8.0-26-generic N/A > linux-firmware1.190.1 > SourcePackage: linux > UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) > dmi.bios.date: 03/09/2018 > dmi.bios.release: 5.3 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.3.0 > dmi.board.name: 0918N8 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: 1.3.0 > dmi.modalias: > dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: > dmi.product.family: Inspiron > dmi.product.name: Inspiron 3180 > dmi.product.sku: 087E > dmi.product.version: 1.3.0 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903467/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903467 Title: screen freeze in mid-session Status in linux package in Ubuntu: Confirmed Bug description: This is a repeat problem to which I attribute to AMD display driver. The problem mostly occur using Firefox with 4 or more tabs open. It's really frustrating to face the prospect of losing data while surfing the net. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: admin-meir 7349 F pulseaudio /dev/snd/controlC0: admin-meir 7349 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Nov 8 15:00:55 2020 InstallationDate: Installed on 2020-09-03 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
Confirmed that with the update e.g upowerd reports are generated -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Triaged Status in bluez source package in Groovy: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 900384] Re: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package
I want to know why no people to solve this question for so many years! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/900384 Title: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package Status in linux package in Ubuntu: Fix Released Status in usbip package in Ubuntu: Fix Released Bug description: I'm on Kubuntu oneiric (11.10), using usbip 0.1.7-3 and kernel linux- image-3.0.0-13-generic. I'm trying to set up USB/IP to share a USB-only printer/scanner over the LAN. However, whenever I try to start the demon, it gives the error message that the usbip_common_mod.ko and usbip.ko kernel modules are required: root@curie:~# usbipd -D usbip err: stub_driver.c: 33 (open_sysfs_stub_driver) usbip_common_mod.ko and usbip.ko must be loaded ** ERROR **: driver open failed Trace/breakpoint trap The package description of usbip says: " USB/IP requires kernel support which is included in Linux kernels 2.6.28 or newer." Unfortunately, I can't find a package that provides those kernel module. I have also installed the usbip-source package, but (1) its /usr/src/modules/usbip/src/README file says: "For newer kernels ( >=2.6.28 ), try linux-staging code!" and (2) trying to build it with m-a also fails: # Build the module cd src && /usr/bin/make KSOURCE=/usr/src/linux HCD_HEADER=/usr/src/modules/usbip/src/headers/hcd.h KBUILD_VERBOSE=0 make[2]: Entering directory `/usr/src/modules/usbip/src' make -C /usr/src/linux LANG=C KBUILD_VERBOSE=0 M=`pwd` modules make[3]: Entering directory `/usr/src/linux-headers-3.0.0-13-generic' CC [M] /usr/src/modules/usbip/src/stub_dev.o /usr/src/modules/usbip/src/stub_dev.c: In function ‘stub_probe’: /usr/src/modules/usbip/src/stub_dev.c:392:42: error: ‘struct device’ has no member named ‘bus_id’ make[4]: *** [/usr/src/modules/usbip/src/stub_dev.o] Error 1 make[3]: *** [_module_/usr/src/modules/usbip/src] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-3.0.0-13-generic' make[2]: *** [default] Error 2 make[2]: Leaving directory `/usr/src/modules/usbip/src' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/usbip' make: *** [kdist_build] Error 2 BUILD FAILED! See /var/cache/modass/usbip.buildlog.3.0.0-13-generic.1323105464 for details. Build failed. Press Return to continue... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
** Changed in: bluez (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in bluez source package in Focal: Invalid Status in apport source package in Groovy: Triaged Status in bluez source package in Groovy: Invalid Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903467] Re: screen freeze in mid-session
One way is to add more swap space and tune swappiness to help the situation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903467 Title: screen freeze in mid-session Status in linux package in Ubuntu: Confirmed Bug description: This is a repeat problem to which I attribute to AMD display driver. The problem mostly occur using Firefox with 4 or more tabs open. It's really frustrating to face the prospect of losing data while surfing the net. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: admin-meir 7349 F pulseaudio /dev/snd/controlC0: admin-meir 7349 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Nov 8 15:00:55 2020 InstallationDate: Installed on 2020-09-03 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** No longer affects: zsys (Ubuntu) ** No longer affects: zsys (Ubuntu Groovy) ** No longer affects: zsys (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in coreutils source package in Focal: Incomplete Status in zfs-linux source package in Focal: Triaged Status in coreutils source package in Groovy: Incomplete Status in zfs-linux source package in Groovy: Triaged Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903619] Re: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10-rc3/amd64/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903619 Title: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390 Status in linux package in Ubuntu: Confirmed Bug description: Filing this bug as per request of Rex Tsai. This is a follow-up to: https://answers.launchpad.net/ubuntu-certification/+question/693893 Synopsis: after powering off, the machine sometimes hangs on the next start. I also added some screenshots there. The interface here only allows a single attachment. Output of fwupdmgr get-devices: 20NR001EGE │ ├─SAMSUNG MZVLB512HAJQ-000L7: │ Device ID: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f │ Summary: NVM Express Solid State Drive │ Current version: 5L2QEXA7 │ Vendor: Samsung Electronics Co Ltd (NVME:0x144D) │ GUIDs: 6e54c992-d302-59ab-b454-2d26ddd63e6d │ 47335265-a509-51f7-841e-1c94911af66b │ 79d6cfae-a5a2-5936-9248-5aebd23480f7 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─System Firmware: │ Device ID: 7eca2f04c4c15ff7cf11f74503846da436b2dff3 │ Current version: 0.1.31 │ Minimum Version: 0.0.1 │ Vendor: LENOVO (DMI:LENOVO) │ GUID: 7d78a18a-80db-4a65-a955-b79f8ca2a334 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Cryptographic hash verification is available │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: 6461040534f2259a0439361986adf73979fd836e │ Current version: 192.68.1606 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: c35736d2-9e47-4578-93e9-68d5b04ea77e │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: ef9c8dc313296d8f84c1815e89219f8ef6948b98 │ Current version: 1.1.4385 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: cb04e55e-456d-41f4-a9ec-24071f5a1f0f │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─UEFI Device Firmware: Device ID: 2d2892da83e97f5a5cd203a1d03dfe7e50d713c2 Current version: 0.73.64 Minimum Version: 0.73.64 Vendor: DMI:LENOVO GUID: 452fb595-c800-4a96-93c4-9668cc335373 Device Flags: • Internal device • Updatable • Requires AC power • Needs a reboot after installation • Device is usable for the duration of the update Output of fwupdmgr get-updates: • SAMSUNG MZVLB512HAJQ-000L7 has the latest available firmware version • System Firmware has no available firmware updates • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwin 1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 02:30:34 2020 InstallationDate: Installed on 2020-11-04 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NR001EGE ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1903619] 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/1903619 Title: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390 Status in linux package in Ubuntu: Confirmed Bug description: Filing this bug as per request of Rex Tsai. This is a follow-up to: https://answers.launchpad.net/ubuntu-certification/+question/693893 Synopsis: after powering off, the machine sometimes hangs on the next start. I also added some screenshots there. The interface here only allows a single attachment. Output of fwupdmgr get-devices: 20NR001EGE │ ├─SAMSUNG MZVLB512HAJQ-000L7: │ Device ID: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f │ Summary: NVM Express Solid State Drive │ Current version: 5L2QEXA7 │ Vendor: Samsung Electronics Co Ltd (NVME:0x144D) │ GUIDs: 6e54c992-d302-59ab-b454-2d26ddd63e6d │ 47335265-a509-51f7-841e-1c94911af66b │ 79d6cfae-a5a2-5936-9248-5aebd23480f7 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─System Firmware: │ Device ID: 7eca2f04c4c15ff7cf11f74503846da436b2dff3 │ Current version: 0.1.31 │ Minimum Version: 0.0.1 │ Vendor: LENOVO (DMI:LENOVO) │ GUID: 7d78a18a-80db-4a65-a955-b79f8ca2a334 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Cryptographic hash verification is available │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: 6461040534f2259a0439361986adf73979fd836e │ Current version: 192.68.1606 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: c35736d2-9e47-4578-93e9-68d5b04ea77e │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: ef9c8dc313296d8f84c1815e89219f8ef6948b98 │ Current version: 1.1.4385 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: cb04e55e-456d-41f4-a9ec-24071f5a1f0f │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─UEFI Device Firmware: Device ID: 2d2892da83e97f5a5cd203a1d03dfe7e50d713c2 Current version: 0.73.64 Minimum Version: 0.73.64 Vendor: DMI:LENOVO GUID: 452fb595-c800-4a96-93c4-9668cc335373 Device Flags: • Internal device • Updatable • Requires AC power • Needs a reboot after installation • Device is usable for the duration of the update Output of fwupdmgr get-updates: • SAMSUNG MZVLB512HAJQ-000L7 has the latest available firmware version • System Firmware has no available firmware updates • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwin 1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 02:30:34 2020 InstallationDate: Installed on 2020-11-04 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NR001EGE ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1895039] Re: General protection fault
[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/1895039 Title: General protection fault Status in linux package in Ubuntu: Expired Bug description: I am using this reposuitory on ubuntu 18.04 with amd 2400g apu. I am experiencing crashes/freezes in chromium-browser. I can find this in dmesg. [ 875.594090] general protection fault, probably for non-canonical address 0x7ed840c139f11979: [#1] SMP NOPTI [ 875.594099] CPU: 0 PID: 284 Comm: kworker/u64:6 Not tainted 5.7.1-050701-generic #202006071230 [ 875.594101] Hardware name: System manufacturer System Product Name/PRIME B350M-A, BIOS 5204 07/29/2019 [ 875.594117] Workqueue: events_unbound commit_work [drm_kms_helper] [ 875.594255] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x270/0x11b0 [amdgpu] [ 875.594258] Code: fe ff ff 48 8b 43 08 8b 90 e0 02 00 00 41 83 c5 01 44 39 ea 0f 87 3a ff ff ff 4c 8b b5 a8 fd ff ff 4d 85 f6 0f 84 ee 00 00 00 <41> 80 be b0 01 00 00 01 0f 86 a1 00 00 00 48 b9 00 00 00 00 01 00 [ 875.594259] RSP: 0018:aa470110fb88 EFLAGS: 00010202 [ 875.594261] RAX: 8edc8e504000 RBX: 8edc6a39f880 RCX: 8edc875d0f00 [ 875.594263] RDX: 0004 RSI: c0eb0a90 RDI: 0002 [ 875.594265] RBP: aa470110fe18 R08: 0001 R09: 0001 [ 875.594266] R10: 9c86a0a0 R11: R12: 8edc6bf43400 [ 875.594267] R13: 0004 R14: 7ed840c139f11979 R15: 8edc6a27dc00 [ 875.594270] FS: () GS:8edc9080() knlGS: [ 875.594272] CS: 0010 DS: ES: CR0: 80050033 [ 875.594273] CR2: 7fd8e05ed010 CR3: 000406368000 CR4: 003406f0 [ 875.594275] Call Trace: [ 875.594284] ? __switch_to_asm+0x40/0x70 [ 875.594286] ? __switch_to_asm+0x34/0x70 [ 875.594289] ? __switch_to_asm+0x40/0x70 [ 875.594291] ? __switch_to_asm+0x34/0x70 [ 875.594293] ? __switch_to_asm+0x40/0x70 [ 875.594295] ? __switch_to_asm+0x34/0x70 [ 875.594297] ? __switch_to_asm+0x40/0x70 [ 875.594299] ? __switch_to_asm+0x34/0x70 [ 875.594301] ? __switch_to_asm+0x40/0x70 [ 875.594304] ? __switch_to_asm+0x34/0x70 [ 875.594306] ? __switch_to_asm+0x40/0x70 [ 875.594308] ? __switch_to_asm+0x34/0x70 [ 875.594310] ? __switch_to_asm+0x40/0x70 [ 875.594312] ? __switch_to_asm+0x34/0x70 [ 875.594314] ? __switch_to_asm+0x40/0x70 [ 875.594316] ? __switch_to_asm+0x34/0x70 [ 875.594318] ? __switch_to_asm+0x40/0x70 [ 875.594320] ? __switch_to_asm+0x34/0x70 [ 875.594322] ? __switch_to_asm+0x40/0x70 [ 875.594324] ? __switch_to_asm+0x34/0x70 [ 875.594326] ? __switch_to_asm+0x40/0x70 [ 875.594328] ? __switch_to_asm+0x34/0x70 [ 875.594330] ? __switch_to_asm+0x40/0x70 [ 875.594332] ? __switch_to_asm+0x34/0x70 [ 875.594335] ? __switch_to_asm+0x40/0x70 [ 875.594336] ? __switch_to_asm+0x34/0x70 [ 875.594338] ? __switch_to_asm+0x40/0x70 [ 875.594342] ? __switch_to+0x157/0x450 [ 875.594344] ? __switch_to_asm+0x40/0x70 [ 875.594345] ? __switch_to_asm+0x34/0x70 [ 875.594348] ? __schedule+0x2e5/0x780 [ 875.594350] ? preempt_schedule_common+0x18/0x30 [ 875.594352] ? _cond_resched+0x19/0x30 [ 875.594354] ? wait_for_completion_timeout+0x3a/0x100 [ 875.594356] ? reschedule_interrupt+0xa/0x20 [ 875.594366] commit_tail+0x99/0x130 [drm_kms_helper] [ 875.594375] commit_work+0x12/0x20 [drm_kms_helper] [ 875.594377] process_one_work+0x1e8/0x3b0 [ 875.594379] worker_thread+0x4d/0x400 [ 875.594382] kthread+0x104/0x140 [ 875.594383] ? process_one_work+0x3b0/0x3b0 [ 875.594384] ? kthread_park+0x90/0x90 [ 875.594386] ret_from_fork+0x22/0x40 [ 875.594388] Modules linked in: edac_mce_amd kvm joydev amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec crct10dif_pclmul snd_hda_core snd_hwdep amd_iommu_v2 gpu_sched crc32_pclmul snd_pcm ttm ghash_clmulni_intel snd_seq_midi drm_kms_helper snd_seq_midi_event cec snd_rawmidi rc_core snd_seq drm snd_seq_device snd_timer aesni_intel i2c_algo_bit pl2303 crypto_simd fb_sys_fops snd syscopyarea eeepc_wmi ch341 cryptd asus_wmi sysfillrect glue_helper usbserial hid_multitouch sparse_keymap wmi_bmof k10temp ccp sysimgblt soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i2c_piix4 r8169 ahci realtek libahci wmi video gpio_amdpt gpio_generic [ 875.594420] ---[ end trace a232a1a96753b9ba ]--- [ 875.594501] RIP: 0010:amdgpu_dm_atomic_commit_tail+0x270/0x11b0 [amdgpu] [ 875.594504] Code: fe ff ff 48 8b 43 08 8b 90 e0
[Kernel-packages] [Bug 1903619] Re: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390
** 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/1903619 Title: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390 Status in linux package in Ubuntu: New Bug description: Filing this bug as per request of Rex Tsai. This is a follow-up to: https://answers.launchpad.net/ubuntu-certification/+question/693893 Synopsis: after powering off, the machine sometimes hangs on the next start. I also added some screenshots there. The interface here only allows a single attachment. Output of fwupdmgr get-devices: 20NR001EGE │ ├─SAMSUNG MZVLB512HAJQ-000L7: │ Device ID: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f │ Summary: NVM Express Solid State Drive │ Current version: 5L2QEXA7 │ Vendor: Samsung Electronics Co Ltd (NVME:0x144D) │ GUIDs: 6e54c992-d302-59ab-b454-2d26ddd63e6d │ 47335265-a509-51f7-841e-1c94911af66b │ 79d6cfae-a5a2-5936-9248-5aebd23480f7 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─System Firmware: │ Device ID: 7eca2f04c4c15ff7cf11f74503846da436b2dff3 │ Current version: 0.1.31 │ Minimum Version: 0.0.1 │ Vendor: LENOVO (DMI:LENOVO) │ GUID: 7d78a18a-80db-4a65-a955-b79f8ca2a334 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Cryptographic hash verification is available │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: 6461040534f2259a0439361986adf73979fd836e │ Current version: 192.68.1606 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: c35736d2-9e47-4578-93e9-68d5b04ea77e │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: ef9c8dc313296d8f84c1815e89219f8ef6948b98 │ Current version: 1.1.4385 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: cb04e55e-456d-41f4-a9ec-24071f5a1f0f │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─UEFI Device Firmware: Device ID: 2d2892da83e97f5a5cd203a1d03dfe7e50d713c2 Current version: 0.73.64 Minimum Version: 0.73.64 Vendor: DMI:LENOVO GUID: 452fb595-c800-4a96-93c4-9668cc335373 Device Flags: • Internal device • Updatable • Requires AC power • Needs a reboot after installation • Device is usable for the duration of the update Output of fwupdmgr get-updates: • SAMSUNG MZVLB512HAJQ-000L7 has the latest available firmware version • System Firmware has no available firmware updates • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwin 1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 02:30:34 2020 InstallationDate: Installed on 2020-11-04 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NR001EGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic
[Kernel-packages] [Bug 1903619] [NEW] Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390
You have been subscribed to a public bug: Filing this bug as per request of Rex Tsai. This is a follow-up to: https://answers.launchpad.net/ubuntu-certification/+question/693893 Synopsis: after powering off, the machine sometimes hangs on the next start. I also added some screenshots there. The interface here only allows a single attachment. Output of fwupdmgr get-devices: 20NR001EGE │ ├─SAMSUNG MZVLB512HAJQ-000L7: │ Device ID: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f │ Summary: NVM Express Solid State Drive │ Current version: 5L2QEXA7 │ Vendor: Samsung Electronics Co Ltd (NVME:0x144D) │ GUIDs: 6e54c992-d302-59ab-b454-2d26ddd63e6d │ 47335265-a509-51f7-841e-1c94911af66b │ 79d6cfae-a5a2-5936-9248-5aebd23480f7 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─System Firmware: │ Device ID: 7eca2f04c4c15ff7cf11f74503846da436b2dff3 │ Current version: 0.1.31 │ Minimum Version: 0.0.1 │ Vendor: LENOVO (DMI:LENOVO) │ GUID: 7d78a18a-80db-4a65-a955-b79f8ca2a334 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Cryptographic hash verification is available │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: 6461040534f2259a0439361986adf73979fd836e │ Current version: 192.68.1606 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: c35736d2-9e47-4578-93e9-68d5b04ea77e │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: ef9c8dc313296d8f84c1815e89219f8ef6948b98 │ Current version: 1.1.4385 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: cb04e55e-456d-41f4-a9ec-24071f5a1f0f │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─UEFI Device Firmware: Device ID: 2d2892da83e97f5a5cd203a1d03dfe7e50d713c2 Current version: 0.73.64 Minimum Version: 0.73.64 Vendor: DMI:LENOVO GUID: 452fb595-c800-4a96-93c4-9668cc335373 Device Flags: • Internal device • Updatable • Requires AC power • Needs a reboot after installation • Device is usable for the duration of the update Output of fwupdmgr get-updates: • SAMSUNG MZVLB512HAJQ-000L7 has the latest available firmware version • System Firmware has no available firmware updates • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwin 1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 02:30:34 2020 InstallationDate: Installed on 2020-11-04 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20NR001EGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=b5cd979c-23c1-4fb8-95cf-9610c6e998db ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET46W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001EGE dmi.board.vendor:
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
In this new systemd timegraph (systemd-time-graph-2.svg) , at the time khaled.service is run, the scheduler had to changed to [none]: from rc.localTue Nov 10 03:39:00 UTC 2020 [mq-deadline] none from myscript.sh Tue Nov 10 03:39:08 UTC 2020 [none] mq-deadline The difference between the first time-graph and the second is that khaled.service was moved to after cloud-config.service has *finished* starting-up. I think this basically confirms that something in cloud-config.service is doing (or triggering somehow) this change. ** Attachment added: "systemd-time-graph-2.svg" https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+attachment/5432873/+files/something.svg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
Still trying to hunt down who is changing that attribute. It is certainly not a kernel change that is causing this new behaviour. Something in userspace is doing it, very late in the boot. In the attached systemd time thingie, at the time that both rc- local.service and khaled.service are run, the scheduler was still mq- deadline: from rc.localTue Nov 10 03:22:15 UTC 2020 [mq-deadline] none from myscript.sh Tue Nov 10 03:22:21 UTC 2020 [mq-deadline] none My guess is that something in cloud-config.service or cloud- final.service is making this change. ** Attachment added: "time thingie showing systemd service times" https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+attachment/5432868/+files/tracing-systemd-1.svg ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728256] Re: Memory corruption in Windows 10 guest / amd64
*** This bug is a duplicate of bug 1738972 *** https://bugs.launchpad.net/bugs/1738972 ** This bug has been marked a duplicate of bug 1738972 [A] KVM Windows BSOD on 4.13.x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728256 Title: Memory corruption in Windows 10 guest / amd64 Status in QEMU: New Status in linux package in Ubuntu: Confirmed Bug description: I have a Win 10 Pro x64 guest inside a qemu/kvm running on an Arch x86_64 host. The VM has a physical GPU passed through, as well as the physical USB controllers, as well as a dedicated SSD attached via SATA; you can find the complete libvirt xml here: https://pastebin.com/U1ZAXBNg I built qemu from source using the qemu-minimal-git AUR package; you can find the build script here: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=qemu-minimal-git (if you aren't familiar with Arch, this is essentially a bash script where build() and package() are run to build the files, and then install them into the $pkgdir to later tar them up.) Starting with qemu v2.10.0, Windows crashes randomly with a bluescreen about CRITICAL_STRUCTURE_CORRUPTION. I also tested the git heads f90ea7ba7c, 861cd431c9 and e822e81e35, before I went back to v2.9.0, which is running stable for over 50 hours right now. During my tests I found that locking the memory pages alleviates the problem somewhat, but never completely avoids it. However, with the crashes occuring randomly, that could as well be false conclusions; I had crashes within minutes after boot with that too. I will now start `git bisect`ing; if you have any other suggestions on what I could try or possible patches feel free to leave them with me. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1728256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Tags added: originate-from-1894066 -- 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/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: 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: Won't Fix Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: New Status in linux source package in Hirsute: Incomplete Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807974] Re: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370
This happens for me quite often on 20.10: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) I can barely stay attached to wifi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807974 Title: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9370 developer edition (Ubuntu version) running Cosmic. A handful of times per day, my wireless stops working ("?" appears in the icon in Network Manager). Turning wireless off and then on again, or suspending and waking the machine up, makes the wireless work again. dmesg output is as follows: $ dmesg | grep ath10k [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 6317c652-4817-4fdd-b6d7-c7b8336e493f) [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 6646.270369] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump: [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3 [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107 [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19 [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8 [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103 [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6 [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1 [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809 [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118 [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 03393f2f-0ce1-4017-b711-40dd14f2ec11) [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [17641.848065] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump: [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3 [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244 [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52 [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5 [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105 [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30 [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1 [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809 [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118 [17642.835601] ath10k_pci :02:00.0: device successfully recovered [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809 [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118 I do not recall having any wireless issues before I upgraded (when this machine was running Bionic). Bug #1730331 - ath10k_pci: firmware crashed! Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10] could be related, but appear to be related to earlier releases, whereas my issue has appeared/become much worse on Cosmic.
[Kernel-packages] [Bug 1903608] Re: NVIDIA module load failure / probe error on GeForce GT 540M
** Summary changed: - NVIDIA probe error + NVIDIA module load failure / probe error on GeForce GT 540M ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) -- 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/1903608 Title: NVIDIA module load failure / probe error on GeForce GT 540M Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After enabling NVIDIA on-demand mode on my PC, I noticed several error logs in dmesg and udevadm monitor related to nvidia driver. Below is a snippet of both: dmesg: 1444.284066] nvidia: probe of :01:00.0 failed with error -1 [ 1444.284099] NVRM: The NVIDIA probe routine failed for 1 device(s). [ 1444.284099] NVRM: None of the NVIDIA graphics adapters were initialized! [ 1444.311875] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238 [ 1444.383106] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [ 1444.383609] NVRM: This is a 64-bit BAR mapped above 4GB by the system NVRM: BIOS or the Linux kernel, but the PCI bridge NVRM: immediately upstream of this GPU does not define NVRM: a matching prefetchable memory window. [ 1444.383610] NVRM: This may be due to a known Linux kernel bug. Please NVRM: see the README section on 64-bit BARs for additional NVRM: information. udevadm monitor KERNEL[2197.606715] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.607201] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.607247] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.626941] remove /kernel/slab/anon_vma/cgroup/anon_vma(21545:nvidia-persistenced.service) (cgroup) KERNEL[2197.645641] remove /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.648117] remove /kernel/slab/:A-128/cgroup/pid(21545:nvidia-persistenced.service) (cgroup) UDEV [2197.667396] remove /kernel/slab/kmalloc-4k/cgroup/kmalloc-4k(21545:nvidia-persistenced.service) (cgroup) KERNEL[2197.677707] remove /module/nvidia (module) UDEV [2197.688181] remove /kernel/slab/kmalloc-512/cgroup/kmalloc-512(21545:nvidia-persistenced.service) (cgroup) UDEV [2197.713995] remove /kernel/slab/kmalloc-64/cgroup/kmalloc-64(21545:nvidia-persistenced.service) (cgroup) KERNEL[2197.726960] add /module/nvidia (module) KERNEL[2197.727742] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.728198] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.728235] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.764326] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.769616] remove /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.775232] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.805688] remove /module/nvidia (module) UDEV [2197.805966] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.816599] remove /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.856459] add /module/nvidia (module) KERNEL[2197.857206] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.857725] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.857757] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.871031] add /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.883148] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.893645] remove /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.912227] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.922880] remove /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.925684] remove /module/nvidia (module please help in addressing this issue. Due to this I noticed systemd- udevd is running 100% of one CPU. Thanks, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 9 20:07:45 2020 DistUpgraded: 2020-11-09 19:22:20,866 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-122-generic, x86_64: installed bbswitch, 0.8, 5.4.0-52-generic, x86_64: installed nvidia, 390.138, 4.15.0-122-generic, x86_64: installed nvidia, 390.138, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd
[Kernel-packages] [Bug 1903292] 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 1903292 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland-session process then brings me back to the GDM login screen and I can start a new session. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-17 (388 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: wayland-session third-party-packages focal Uname: Linux 5.9.0 x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (194 days ago) UserGroups: adm cdrom dip disk docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903608] [NEW] NVIDIA module load failure / probe error on GeForce GT 540M
You have been subscribed to a public bug: After enabling NVIDIA on-demand mode on my PC, I noticed several error logs in dmesg and udevadm monitor related to nvidia driver. Below is a snippet of both: dmesg: 1444.284066] nvidia: probe of :01:00.0 failed with error -1 [ 1444.284099] NVRM: The NVIDIA probe routine failed for 1 device(s). [ 1444.284099] NVRM: None of the NVIDIA graphics adapters were initialized! [ 1444.311875] nvidia-nvlink: Unregistered the Nvlink Core, major device number 238 [ 1444.383106] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [ 1444.383609] NVRM: This is a 64-bit BAR mapped above 4GB by the system NVRM: BIOS or the Linux kernel, but the PCI bridge NVRM: immediately upstream of this GPU does not define NVRM: a matching prefetchable memory window. [ 1444.383610] NVRM: This may be due to a known Linux kernel bug. Please NVRM: see the README section on 64-bit BARs for additional NVRM: information. udevadm monitor KERNEL[2197.606715] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.607201] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.607247] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.626941] remove /kernel/slab/anon_vma/cgroup/anon_vma(21545:nvidia-persistenced.service) (cgroup) KERNEL[2197.645641] remove /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.648117] remove /kernel/slab/:A-128/cgroup/pid(21545:nvidia-persistenced.service) (cgroup) UDEV [2197.667396] remove /kernel/slab/kmalloc-4k/cgroup/kmalloc-4k(21545:nvidia-persistenced.service) (cgroup) KERNEL[2197.677707] remove /module/nvidia (module) UDEV [2197.688181] remove /kernel/slab/kmalloc-512/cgroup/kmalloc-512(21545:nvidia-persistenced.service) (cgroup) UDEV [2197.713995] remove /kernel/slab/kmalloc-64/cgroup/kmalloc-64(21545:nvidia-persistenced.service) (cgroup) KERNEL[2197.726960] add /module/nvidia (module) KERNEL[2197.727742] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.728198] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.728235] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.764326] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.769616] remove /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.775232] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.805688] remove /module/nvidia (module) UDEV [2197.805966] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.816599] remove /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.856459] add /module/nvidia (module) KERNEL[2197.857206] add /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.857725] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.857757] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.871031] add /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.883148] add /bus/pci/drivers/nvidia (drivers) KERNEL[2197.893645] remove /kernel/slab/nvidia_stack_cache (slab) UDEV [2197.912227] remove /bus/pci/drivers/nvidia (drivers) UDEV [2197.922880] remove /kernel/slab/nvidia_stack_cache (slab) KERNEL[2197.925684] remove /module/nvidia (module please help in addressing this issue. Due to this I noticed systemd- udevd is running 100% of one CPU. Thanks, Jeff ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 9 20:07:45 2020 DistUpgraded: 2020-11-09 19:22:20,866 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-122-generic, x86_64: installed bbswitch, 0.8, 5.4.0-52-generic, x86_64: installed nvidia, 390.138, 4.15.0-122-generic, x86_64: installed nvidia, 390.138, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 540M] [1028:050e] InstallationDate: Installed on 2019-01-16 (663 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic
[Kernel-packages] [Bug 1903292] Re: System hangs after suspend
** Summary changed: - GNOME Wayland session hangs after suspend + System hangs after suspend ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1903292 Title: System hangs after suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland-session process then brings me back to the GDM login screen and I can start a new session. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-17 (388 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: wayland-session third-party-packages focal Uname: Linux 5.9.0 x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (194 days ago) UserGroups: adm cdrom dip disk docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903292] [NEW] System hangs after suspend
You have been subscribed to a public bug: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland-session process then brings me back to the GDM login screen and I can start a new session. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-17 (388 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: wayland-session third-party-packages focal Uname: Linux 5.9.0 x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (194 days ago) UserGroups: adm cdrom dip disk docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal third-party-packages wayland wayland-session -- System hangs after suspend https://bugs.launchpad.net/bugs/1903292 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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
We're not 100% sure what fixes are required but it looks like it will require fixes in the kernel AND bluez AND pulseaudio. The first two are included in Ubuntu 20.10 already, but that's not enough to fix this bug. If you want to track the main work outstanding then please look at: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/776 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/288 It seems the PulseAudio developers are targeting future version 15. That will take a while because even version 14 isn't released yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903570] Re: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output"
*** This bug is a duplicate of bug 1901922 *** https://bugs.launchpad.net/bugs/1901922 ** This bug has been marked a duplicate of bug 1901922 [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1903570 Title: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output" Status in alsa-lib package in Ubuntu: Confirmed Bug description: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
lspci | grep -i network 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03) sudo lshw -C network *-network UNCLAIMED description: Network controller product: BCM4352 802.11ac Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:02:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:ed40-ed407fff memory:ed20-ed3f *-network description: Ethernet interface physical id: 1 bus info: usb@2:2 logical name: enx000edab6c1eb serial: 00:0e:da:b6:c1:eb size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=ax88179_178a driverversion=5.8.0-26-generic duplex=full ip=192.168.0.167 link=yes multicast=yes port=MII speed=1Gbit/s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] 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 1903612 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: 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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: Incomplete Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903612] [NEW] Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Public bug reported: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in linux package in Ubuntu: New Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
sda is definitely being registered as mq-deadline .. and it appears to remain that way until quite late in the boot. But then something is changing the sda scheduler later at some point. No luck so far determining what is making that later change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Changed in: zsys (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: zsys (Ubuntu Groovy) Status: Confirmed => Invalid ** Changed in: coreutils (Ubuntu Focal) Status: Confirmed => Incomplete ** Changed in: coreutils (Ubuntu Groovy) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in coreutils source package in Focal: Incomplete Status in zfs-linux source package in Focal: Triaged Status in zsys source package in Focal: Invalid Status in coreutils source package in Groovy: Incomplete Status in zfs-linux source package in Groovy: Triaged Status in zsys source package in Groovy: Invalid Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 and kernel crash on GeForce GTX 1060 6GB
Can confirm with 20.04 (not new though, this happened in 18.04 too): - GTX 1050 Ti, drivers 450.80.02 - Kernel 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux - dmesg attached - I have to ssh into the machine and shut it down. For me, it always seem to happen when I walk away after locking my screen and turning off my monitor (by turning it off at the power bar - an old work around for failing-to-sleep-monitor issues, of all things) Note my keyboard and mice a plugged into the hub, so you'll see usb disconnects in the dmesg. ** Attachment added: "dmesg output" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+attachment/5432773/+files/dmesg2.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 and kernel crash on GeForce GTX 1060 6GB Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed 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:
[Kernel-packages] [Bug 1891502] Re: tpm tpm0: Error (28) sending savestate before suspend
Attached dmesg after 2 suspend cycles on 5.0.0rc8 ** Attachment added: "dmesg.out2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891502/+attachment/5432772/+files/dmesg.out2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891502 Title: tpm tpm0: Error (28) sending savestate before suspend Status in linux package in Ubuntu: Incomplete Bug description: Upon clicking suspend via Log Out... button in Xubuntu and also via systemctl suspend, the screen turns to black for 2 sec but then brings me back to log in screen instead of suspending. This was not an issue in 18.04. Currently on fresh install of 20.04.1. Aug 13 08:12:59 laptop kernel: [87528.628302] PM: suspend entry (s2idle) Aug 13 08:13:00 laptop kernel: [87529.250844] printk: Suspending console(s) (use no_console_suspend to debug) Aug 13 08:13:00 laptop kernel: [87529.250844] printk: Suspending console(s) (use no_console_suspend to debug) Aug 13 08:13:00 laptop kernel: [87529.555272] tpm tpm0: Error (28) sending savestate before suspend Aug 13 08:13:00 laptop kernel: [87529.555287] PM: __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x80 returns 28 Aug 13 08:13:00 laptop kernel: [87529.555292] PM: dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 28 Aug 13 08:13:00 laptop kernel: [87529.555296] PM: Device 00:01 failed to suspend: error 28 Aug 13 08:13:00 laptop kernel: [87529.929361] PM: Some devices failed to suspend, or early wake event detected Aug 13 08:13:01 laptop kernel: [87530.458095] PM: suspend exit Aug 13 08:13:01 laptop systemd[1]: systemd-suspend.service: Succeeded. 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.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: smrtalec 1174 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Aug 13 08:25:19 2020 InstallationDate: Installed on 2020-08-10 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Compaq 2510p Notebook PC PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bf5ecda3-8bba-45a8-8f73-038836aa1952 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: 11/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MSP Ver. F.30 dmi.board.name: 30C9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 75.28 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MSPVer.F.30:bd11/11/2011:svnHewlett-Packard:pnHPCompaq2510pNotebookPC:pvrF.30:rvnHewlett-Packard:rn30C9:rvrKBCVersion75.28:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 2510p Notebook PC dmi.product.sku: KR918UT#ABA dmi.product.version: F.30 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903570] Re: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output"
Can confirm, updated: libasound2-data:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1) and libasound2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1) and only have dummy output. Downgraded and it works again. Also broken when testing Groovy Gorilla. Thinkpad T14s, Ryzen 4750U. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1903570 Title: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output" Status in alsa-lib package in Ubuntu: Confirmed Bug description: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903570] Re: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output"
Probably duplicate of https://bugs.launchpad.net/ubuntu/+source/alsa- lib/+bug/1901922 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1903570 Title: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output" Status in alsa-lib package in Ubuntu: Confirmed Bug description: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903570] Re: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-lib (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1903570 Title: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output" Status in alsa-lib package in Ubuntu: Confirmed Bug description: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
I reported this today, didn't realise an extensive bug report already exists: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570 Lenovo S540-13ARE (AMD Ryzen 4800u). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-lib source package in Focal: In Progress Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-ucm-conf source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: In Progress Status in alsa-ucm-conf source package in Hirsute: In Progress Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias:
Re: [Kernel-packages] [Bug 1903467] Re: screen freeze in mid-session
thanks for the reply kai-heng.This laptop (Dell Inspiron 3180 w/ AMD processor & graphic driver) originally came with Windows 10 OS. I simply replaced it with ubuntu OS.If 4G is suffeciante for Windows - it should also be suffeciante for ubuntu. Besides, the motherboard does not have additional slot for memory expansion.In my view, the AMD driver needs to be upgraded to accomoted a btter memory mangement. Because as far as I know the same laptop with Intel processors does not seem to have the same issues. Otherwise I have to close more apps running in the background - until hopefuly AMD willfix this problem. Levi On Sunday, November 8, 2020, 11:35:40 PM PST, Kai-Heng Feng <1903...@bugs.launchpad.net> wrote: Could be caused by 4G ram... it's not enough for modern browsers... -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1903467 Title: screen freeze in mid-session Status in linux package in Ubuntu: Confirmed Bug description: This is a repeat problem to which I attribute to AMD display driver. The problem mostly occur using Firefox with 4 or more tabs open. It's really frustrating to face the prospect of losing data while surfing the net. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: admin-meir 7349 F pulseaudio /dev/snd/controlC0: admin-meir 7349 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Nov 8 15:00:55 2020 InstallationDate: Installed on 2020-09-03 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware 1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903467/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903467 Title: screen freeze in mid-session Status in linux package in Ubuntu: Confirmed Bug description: This is a repeat problem to which I attribute to AMD display driver. The problem mostly occur using Firefox with 4 or more tabs open. It's really frustrating to face the prospect of losing data while surfing the net. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: admin-meir 7349 F pulseaudio /dev/snd/controlC0: admin-meir 7349 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Nov 8 15:00:55 2020 InstallationDate: Installed on 2020-09-03 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=a76d7df4-e22a-430d-8de3-9b5c2661d64e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-04 (4 days ago) dmi.bios.date: 03/09/2018
[Kernel-packages] [Bug 1903570] Re: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output"
** Summary changed: - After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. + libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1903570 Title: libasound2 and libasound2-data update replaces all audio outputs with "Dummy Output" Status in alsa-lib package in Ubuntu: New Bug description: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903570] [NEW] After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenov
Public bug reported: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-lib (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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1903570 Title: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Status in alsa-lib package in Ubuntu: New Bug description: After updating libasound2 and libasound2-data the only audio output device is "Dummy Output". Rolling back to prev version solves it. AMD Ryzen 4800u laptop Lenovo S540-13ARE. Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libasound2 1.2.2-2.1ubuntu2.1 Uname: Linux 5.8.18-050818-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Nov 9 18:23:28 2020 InstallationDate: Installed on 2020-08-30 (71 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1903570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
Strangely: [0.743029] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [0.744256] io scheduler mq-deadline registered -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
@colin-king dmesg output: [0.00] Linux version 5.8.0-1008-gcp (buildd@lgw01-amd64-043) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #8-Ubuntu SMP Thu Oct 15 12:48:27 UTC 2020 (Ubuntu 5.8.0-1008.8-gcp 5.8.14) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-1008-gcp root=PARTUUID=506f6274-5923-4632-96d5-b96445cc673c ro console=ttyS0 panic=-1 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0fff] reserved [0.00] BIOS-e820: [mem 0x1000-0x00054fff] usable [0.00] BIOS-e820: [mem 0x00055000-0x0005] reserved [0.00] BIOS-e820: [mem 0x0006-0x00097fff] usable [0.00] BIOS-e820: [mem 0x00098000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbe11dfff] usable [0.00] BIOS-e820: [mem 0xbe11e000-0xbe120fff] ACPI data [0.00] BIOS-e820: [mem 0xbe121000-0xbe121fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbe122000-0xbe2d1fff] usable [0.00] BIOS-e820: [mem 0xbe2d2000-0xbe2d9fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbe2da000-0xbe31afff] reserved [0.00] BIOS-e820: [mem 0xbe31b000-0xbf39afff] usable [0.00] BIOS-e820: [mem 0xbf39b000-0xbf3f2fff] reserved [0.00] BIOS-e820: [mem 0xbf3f3000-0xbf3fafff] ACPI data [0.00] BIOS-e820: [mem 0xbf3fb000-0xbf3fefff] ACPI NVS [0.00] BIOS-e820: [mem 0xbf3ff000-0xbffd] usable [0.00] BIOS-e820: [mem 0xbffe-0xbfff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00013fff] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.70 by EDK II [0.00] efi: TPMFinalLog=0xbe2d2000 ACPI=0xbf3fa000 ACPI 2.0=0xbf3fa014 SMBIOS=0xbf3cd000 MEMATTR=0xbe6d3698 RNG=0xbf3cec98 TPMEventLog=0xbd8b6018 [0.00] efi: seeding entropy pool [0.00] random: fast init done [0.00] secureboot: Secure boot disabled [0.00] SMBIOS 2.4 present. [0.00] DMI: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [0.00] Hypervisor detected: KVM [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr 45401001, primary cpu clock [0.00] kvm-clock: using sched offset of 8055433513 cycles [0.03] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.05] tsc: Detected 2300.000 MHz processor [0.89] e820: update [mem 0x-0x0fff] usable ==> reserved [0.91] e820: remove [mem 0x000a-0x000f] usable [0.96] last_pfn = 0x14 max_arch_pfn = 0x4 [0.000131] MTRR default type: write-back [0.000131] MTRR fixed ranges enabled: [0.000132] 0-9 write-back [0.000133] A-F uncachable [0.000134] MTRR variable ranges enabled: [0.000135] 0 base C000 mask 3FFFC000 uncachable [0.000136] 1 base 0100 mask 3F00 uncachable [0.000137] 2 disabled [0.000137] 3 disabled [0.000138] 4 disabled [0.000138] 5 disabled [0.000139] 6 disabled [0.000139] 7 disabled [0.000147] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.000157] last_pfn = 0xbffe0 max_arch_pfn = 0x4 [0.017358] check: Scanning 1 areas for low memory corruption [0.017395] Using GB pages for direct mapping [0.018424] secureboot: Secure boot disabled [0.018442] ACPI: Early table checksum verification disabled [0.018447] ACPI: RSDP 0xBF3FA014 24 (v02 Google) [0.018451] ACPI: XSDT 0xBF3F90E8 5C (v01 Google GOOGFACP 0001 0113) [0.018458] ACPI: FACP 0xBF3F4000 F4 (v02 Google GOOGFACP 0001 GOOG 0001) [0.018465] ACPI: DSDT 0xBF3F5000 0018BA (v01 Google GOOGDSDT 0001 GOOG 0001) [0.018474] ACPI: FACS 0xBE121000 40 [0.018477] ACPI: SSDT 0xBF3F8000 000316 (v02 GOOGLE Tpm2Tabl 1000 INTL 20160527) [
[Kernel-packages] [Bug 1890641] Re: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
I too have the same error, I received the following after running an apt upgrade W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169 W: Possible missing firmware /lib/firmware/amdgpu/renoir_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_vcn.bin for module amdgpu in my case downloading from the link above and doing the following fixed the errors for me. sudo cp -R amdgpu/renoir_* /lib/firmware/amdgpu/ sudo cp -R rtl_nic/rtl8* /lib/firmware/rtl_nic/ sudo update-initramfs -u Thanks @faloz2416 Mo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1890641 Title: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 after running sudo apt upgrade in ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 22:38:31 2020 InstallationDate: Installed on 2019-06-16 (417 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-03-08 22:54:00.439353 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1890641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
I have two monitors connected 1080p 60hz. I have tried with either HTMI or DP, issue is present no matter the combination. I'll also note that I lose my sound settings quite often and need to switch that back to HDMI after any hiccups. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: In Progress Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. 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/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea 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: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
Also Bus 002 Device 006: ID 059f:105f LaCie, Ltd 2Big Quadra USB3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
lspci | grep -i network 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4352 802.11ac Wireless Network Adapter (rev 03) sudo lshw -C network *-network UNCLAIMED description: Network controller product: BCM4352 802.11ac Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:02:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:ed40-ed407fff memory:ed20-ed3f *-network description: Ethernet interface physical id: 1 bus info: usb@2:2 logical name: enx000edab6c1eb serial: 00:0e:da:b6:c1:eb size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=ax88179_178a driverversion=5.8.0-26-generic duplex=full ip=192.168.0.167 link=yes multicast=yes port=MII speed=1Gbit/s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
on a fresh ubuntu 20.10 install ( not upgrade ) seeing same bug wifi not working in settings option to change wifi is grayed out able to reach internet OK using ethernet x86_64 5.8.0-26-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.10 DISTRIB_CODENAME=groovy DISTRIB_DESCRIPTION="Ubuntu 20.10" uname -a Linux andes 5.8.0-26-generic #27-Ubuntu SMP Wed Oct 21 22:29:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux dpkg -l|grepbcmwl ii bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 amd64Broadcom 802.11 Linux STA wireless driver source olaf@andes ~ $ sudo apt-get remove --purge bcmwl-kernel-source sudo apt-get install broadcom-sta-source ran OK sudo apt-get install broadcom-sta-source -y Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: dkms Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: module-assistant The following NEW packages will be installed: broadcom-sta-source module-assistant 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 2,308 kB of archives. After this operation, 2,639 kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu groovy/multiverse amd64 broadcom-sta-source all 6.30.223.271-14 [2,218 kB] Get:2 http://us.archive.ubuntu.com/ubuntu groovy/universe amd64 module-assistant all 0.11.10 [90.3 kB] Fetched 2,308 kB in 1s (2,106 kB/s) Requesting to save current system state Successfully saved as "autozsys_iyujmr" Selecting previously unselected package broadcom-sta-source. (Reading database ... 210357 files and directories currently installed.) Preparing to unpack .../broadcom-sta-source_6.30.223.271-14_all.deb ... Unpacking broadcom-sta-source (6.30.223.271-14) ... Selecting previously unselected package module-assistant. Preparing to unpack .../module-assistant_0.11.10_all.deb ... Unpacking module-assistant (0.11.10) ... Setting up broadcom-sta-source (6.30.223.271-14) ... Setting up module-assistant (0.11.10) ... Processing triggers for man-db (2.9.3-2) ... ZSys is adding automatic system snapshot to GRUB menu sudo apt-get install broadcom-sta-dkms -y Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: broadcom-sta-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2,210 kB of archives. After this operation, 14.5 MB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu groovy/multiverse amd64 broadcom-sta-dkms all 6.30.223.271-14 [2,210 kB] Fetched 2,210 kB in 0s (5,178 kB/s) Requesting to save current system state Successfully saved as "autozsys_x9zm88" Selecting previously unselected package broadcom-sta-dkms. (Reading database ... 210406 files and directories currently installed.) Preparing to unpack .../broadcom-sta-dkms_6.30.223.271-14_all.deb ... Unpacking broadcom-sta-dkms (6.30.223.271-14) ... Setting up broadcom-sta-dkms (6.30.223.271-14) ... Loading new broadcom-sta-6.30.223.271 DKMS files... Building for 5.8.0-26-generic Building initial module for 5.8.0-26-generic Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information. dpkg: error processing package broadcom-sta-dkms (--configure): installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: broadcom-sta-dkms ZSys is adding automatic system snapshot to GRUB menu E: Sub-process /usr/bin/dpkg returned an error code (1) sudo apt-get install broadcom-sta-source -y Reading package lists... Done Building dependency tree Reading state information... Done broadcom-sta-source is already the newest version (6.30.223.271-14). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Requesting to save current system state Successfully saved as "autozsys_57lmb7" Setting up broadcom-sta-dkms (6.30.223.271-14) ... Removing old broadcom-sta-6.30.223.271 DKMS files... -- Deleting module version: 6.30.223.271 completely from the DKMS tree. -- Done. Loading new broadcom-sta-6.30.223.271 DKMS files... Building for 5.8.0-26-generic Building initial module for 5.8.0-26-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/broadcom-sta-dkms.0.crash' Error! Bad return status for module build on kernel: 5.8.0-26-generic (x86_64) Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information. dpkg: error processing package broadcom-sta-dkms (--configure): installed broadcom-sta-dkms package
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
Can you provide the output from dmesg so we can get an idea of what is happening during boot? ** Changed in: linux-gcp (Ubuntu) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] [NEW] Block device scheduler should be multiqueue for spinning disks
Public bug reported: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: New Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Well, reason could by anything. Most users of this chip version don't have this problem, so it may be the BIOS. Is known meanwhile whether any (mainline) kernel version is fine on this system (so that issue can be bisected)? Also interesting would be whether the issue happens with r8168 too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Subscribe r8169 maintainer Heiner Kallweit... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX:
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Hi Kai-Heng, Here is the (much longer) trace from that kernel. Thanks! kernel: [ cut here ] kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out kernel: WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x24c/0x250 kernel: Modules linked in: scsi_transport_iscsi binfmt_misc veth nft_masq xt_comment iptable_mangle iptable_nat bpfilter dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink rdma_ucm ib_uverbs rdma_cm iw_cm ib_cm ib_core overlay snd_hda_codec_realtek nls_iso8859> kernel: autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_crypt hid_logitech_hidpp hid_microsoft ff_memless hid_logitech_dj hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper i2c_piix4 r8169 nvme ahci i2c_nvidia_gpu xhci_pci realtek nvme_core libahci xhci_pci_renesas wmi gpio_amdpt gpio_generic kernel: CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.10.0-051000rc2-generic #202011012330 kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 kernel: RIP: 0010:dev_watchdog+0x24c/0x250 kernel: Code: 5a 94 fd ff eb ab 4c 89 ff c6 05 e2 58 4d 01 01 e8 99 4c fa ff 44 89 e9 4c 89 fe 48 c7 c7 48 35 48 97 48 89 c2 e8 2a 69 16 00 <0f> 0b eb 8c 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 ff 41 56 41 55 kernel: RSP: 0018:a5e700210e90 EFLAGS: 00010286 kernel: RAX: RBX: 9a1800d12e00 RCX: kernel: RDX: 9a1b0eea8ca0 RSI: 9a1b0ee98980 RDI: 0300 kernel: RBP: a5e700210ec0 R08: R09: a5e700210c70 kernel: R10: a5e700210c68 R11: 97b52ca8 R12: 9a1800d12e80 kernel: R13: R14: 9a18008164c0 R15: 9a1800816000 kernel: FS: () GS:9a1b0ee8() knlGS: kernel: CS: 0010 DS: ES: CR0: 80050033 kernel: CR2: 55cfd3d2d008 CR3: 000107f48000 CR4: 003506e0 kernel: Call Trace: kernel: kernel: ? pfifo_fast_enqueue+0x150/0x150 kernel: call_timer_fn+0x2e/0x100 kernel: __run_timers.part.0+0x1d8/0x250 kernel: ? ktime_get+0x3e/0xa0 kernel: ? lapic_next_event+0x21/0x30 kernel: ? clockevents_program_event+0x8f/0xe0 kernel: run_timer_softirq+0x2a/0x50 kernel: __do_softirq+0xce/0x281 kernel: asm_call_irq_on_stack+0x12/0x20 kernel: kernel: do_softirq_own_stack+0x3d/0x50 kernel: irq_exit_rcu+0x95/0xd0 kernel: sysvec_apic_timer_interrupt+0x3d/0x90 kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x360 kernel: Code: 3d e9 64 88 69 e8 64 31 75 ff 49 89 c6 0f 1f 44 00 00 31 ff e8 f5 3c 75 ff 80 7d d7 00 0f 85 01 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 ff 0f 88 0d 01 00 00 49 63 cf 4c 2b 75 c8 48 8d 04 49 48 89 kernel: RSP: 0018:a5e700137e60 EFLAGS: 0246 kernel: RAX: 9a1b0eeac480 RBX: 0002 RCX: 001f kernel: RDX: RSI: 239f5376 RDI: kernel: RBP: a5e700137e98 R08: 0009851dc34e R09: 0400 kernel: R10: 000321ae R11: R12: 9a1801249800 kernel: R13: 97c6c6a0 R14: 0009851dc34e R15: 0002 kernel: cpuidle_enter+0x2e/0x40 kernel: cpuidle_idle_call+0x132/0x1d0 kernel: do_idle+0x7a/0xe0 kernel: cpu_startup_entry+0x20/0x30 kernel: start_secondary+0x90/0xa0 kernel: secondary_startup_64_no_verify+0xb8/0xbb kernel: CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.10.0-051000rc2-generic #202011012330 kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 kernel: Call Trace: kernel: kernel: show_stack+0x52/0x58 kernel: dump_stack+0x70/0x8b kernel: ? dev_watchdog+0x24c/0x250 kernel: __warn.cold+0x24/0x77 kernel: ? dev_watchdog+0x24c/0x250 kernel: report_bug+0xa1/0xc0 kernel: ? __irq_work_queue_local+0x48/0x60 kernel: handle_bug+0x3e/0xa0 kernel: exc_invalid_op+0x19/0x70 kernel: asm_exc_invalid_op+0x12/0x20 kernel: RIP: 0010:dev_watchdog+0x24c/0x250 kernel: Code: 5a 94 fd ff eb ab 4c 89 ff c6 05 e2 58 4d 01 01 e8 99 4c fa ff 44 89 e9 4c 89 fe 48 c7 c7 48 35 48 97 48 89 c2 e8 2a 69 16 00 <0f> 0b eb 8c 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 ff 41 56 41 55 kernel: RSP: 0018:a5e700210e90 EFLAGS: 00010286 kernel: RAX: RBX: 9a1800d12e00 RCX: kernel: RDX: 9a1b0eea8ca0 RSI: 9a1b0ee98980 RDI: 0300 kernel: RBP: a5e700210ec0 R08: R09: a5e700210c70 kernel: R10: a5e700210c68 R11: 97b52ca8 R12: 9a1800d12e80 kernel: R13: R14: 9a18008164c0 R15: 9a1800816000 kernel: ? pfifo_fast_enqueue+0x150/0x150 kernel: call_timer_fn+0x2e/0x100 kernel: __run_timers.part.0+0x1d8/0x250 kernel: ? ktime_get+0x3e/0xa0 kernel: ?
[Kernel-packages] [Bug 1903541] [NEW] groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05
Public bug reported: Upstream raspberrypi patchset 2020-11-05 Ported from the following raspberrypi branch: rpi-5.8.y from https://github.com/raspberrypi/linux.git ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New -- 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/1903541 Title: groovy/linux-raspi: Upstream raspberrypi patchset 2020-11-05 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: New Bug description: Upstream raspberrypi patchset 2020-11-05 Ported from the following raspberrypi branch: rpi-5.8.y from https://github.com/raspberrypi/linux.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1903541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
I confirm, still there in 20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same bug affects me, I'm running 20.04 on an Asus Zenbook and can confirm that removing "quiet splash" DOES NOT resolve the boot issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901417] Re: zfs mount segmentation fault when target directory is non empty
I wonder if this is an issue with one of the dependency libraries that got updated and now the bug does not occur. So far I can't reproduce this issue either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1901417 Title: zfs mount segmentation fault when target directory is non empty Status in zfs-linux package in Ubuntu: Incomplete Bug description: Hi, I just had made some mistake in a mounting order, thus producing non- empty target directory. Imagine a pool name pool1 and zfs filesystems pool1 and pool1/a which are (due to different encryption keys) to be mounted as /pool1/a one in another. (Because of encryption not automatically mounted) I made a simple mistake and mounted /pool1/a before /pool1, but noticed and unmounted /pool1/a before mounting /pool1, but forget to rmdir /pool1/a, so /pool1 was not empty when mounting /pool1. # zfs mount -a cannot mount '/pool1': directory is not empty zsh: segmentation fault (core dumped) zfs mount -a Segmentation faults should not happen. after rmdir /pool1/a (i.e. make the target empty), things work as normal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Oct 25 15:28:45 2020 InstallationDate: Installed on 2018-04-30 (909 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-10-02 (23 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1901417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Hello Having the same problem, running on a Dell XPS 13 9310. when having a look at /sys/power/mem_sleep though, I ONLY see `s2idle` as options. $ sudo cat /sys/power/mem_sleep [s2idle] And when I try to change the file, I get the same errors as Eduardo. Running 5.8.0-26-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899626] Re: Backlight does not work on the legion 5 15arh
I do have the same bug here on Linux 5.8.18-1-MANJARO x86_64 20.2 Nibia, also this been discussed here : https://www.reddit.com/r/archlinux/comments/ihtlzj/problem_with_screen_backlight_regulation_in/ I think my backlight keys were working before installing core/amd-ucode but I'm not sure. Got Lenovo Legion 5-15ARH05 Type 82B5 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/1899626 Title: Backlight does not work on the legion 5 15arh Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: Backlight keys/backlight control does not work. cat /sys/class/backlight/amdgpu_bl0/actual_brightness outputs 311 which is above the max brightness. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tanapoom 1505 F pulseaudio /dev/snd/controlC0: tanapoom 1505 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 21:20:31 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: LENOVO 82B5 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-22-generic root=UUID=a967ce85-0dda-4707-871b-69cbcbcf0b4e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrEUCN26WW:bd08/19/2020:br1.26:efr1.26:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK: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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899626] Re: Backlight does not work on the legion 5 15arh
** 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/1899626 Title: Backlight does not work on the legion 5 15arh Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Bug description: Backlight keys/backlight control does not work. cat /sys/class/backlight/amdgpu_bl0/actual_brightness outputs 311 which is above the max brightness. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-22-generic 5.8.0-22.23 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tanapoom 1505 F pulseaudio /dev/snd/controlC0: tanapoom 1505 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 21:20:31 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: LENOVO 82B5 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-22-generic root=UUID=a967ce85-0dda-4707-871b-69cbcbcf0b4e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-22-generic N/A linux-backports-modules-5.8.0-22-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2020 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrEUCN26WW:bd08/19/2020:br1.26:efr1.26:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK: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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881505] Re: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7
It seems that the 1.6 version of the SOF firmware fixes the issue for me. Haven't got any of those DSP panic messages anymore after the update and before the update they occurred almost every day. Is there anything I can do to help in making this fix to be included to linux-firmware package? Eugene: Have you tried if your issue is fixed by the newer firmware? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1881505 Title: Sound w/SOF driver sporadically fails on Lenovo Carbon X1 gen 7 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Now and then, the notebooks stops producing any sound, and program that try to use sound output freeze for many seconds. There is a repeating sequence on messages in `dmesg`: [116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001 size 120 [116525.402081] sof-audio-pci :00:1f.3: status: fw entered - code 0005 [116525.402338] sof-audio-pci :00:1f.3: error: can't enter idle [116525.402342] sof-audio-pci :00:1f.3: error: trace point 4000 [116525.402346] sof-audio-pci :00:1f.3: error: panic at src/lib/agent.c:50 [116525.402350] sof-audio-pci :00:1f.3: error: DSP Firmware Oops [116525.402356] sof-audio-pci :00:1f.3: EXCCAUSE 0x003f EXCVADDR 0x PS 0x00060925 SAR 0x [116525.402361] sof-audio-pci :00:1f.3: EPC1 0x EPC2 0xbe00d30e EPC3 0x EPC40x [116525.402365] sof-audio-pci :00:1f.3: EPC5 0x EPC6 0x EPC7 0x DEPC0x [116525.402369] sof-audio-pci :00:1f.3: EPS2 0x00060d20 EPS3 0x EPS4 0x EPS50x [116525.402374] sof-audio-pci :00:1f.3: EPS6 0x EPS7 0x INTENABL 0x INTERRU 0x0222 [116525.402378] sof-audio-pci :00:1f.3: stack dump from 0xbe04f5b0 [116525.402385] sof-audio-pci :00:1f.3: 0xbe04f5b0: be00fc00 be04f5e0 be062180 0001 [116525.402391] sof-audio-pci :00:1f.3: 0xbe04f5b4: 0032 [116525.402396] sof-audio-pci :00:1f.3: 0xbe04f5b8: 69cd0100 15655b6c 602aeaf8 93a4 [116525.402401] sof-audio-pci :00:1f.3: 0xbe04f5bc: 93a4 303a3030 [116525.402406] sof-audio-pci :00:1f.3: 0xbe04f5c0: 0078 602aea98 93a4 [116525.402411] sof-audio-pci :00:1f.3: 0xbe04f5c4: 6bdcfb58 93a4 5d006830 93a4 [116525.402416] sof-audio-pci :00:1f.3: 0xbe04f5c8: 6ba37218 93a4 82317aaf bca5 [116525.402421] sof-audio-pci :00:1f.3: 0xbe04f5cc: 6ba37220 93a4 023179f8 bca5 [116525.402446] sof-audio-pci :00:1f.3: error: hda irq intsts 0x intlctl 0xc081 rirb 00 [116525.402450] sof-audio-pci :00:1f.3: error: dsp irq ppsts 0x adspis 0x [116525.402471] sof-audio-pci :00:1f.3: error: host status 0x dsp status 0x mask 0x0003 [116525.402475] sof-audio-pci :00:1f.3: error: waking up any trace sleepers [116525.402481] sof-audio-pci :00:1f.3: error: failed to set dai config for iDisp1 [116525.402486] sof-audio-pci :00:1f.3: ASoC: can't set iDisp1 Pin hw params: -110 [116525.402498] iDisp1: ASoC: hw_params BE failed -110 [116525.402502] HDMI1: ASoC: hw_params BE failed -110 This _might_ be the upstream bug https://github.com/thesofproject/sof/issues/2828 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crosser 42712 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 20:40:20 2020 InstallationDate: Installed on 2020-01-02 (149 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: LENOVO 20QDCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1902795] Re: PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc2
** Summary changed: - PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 + PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc2 Status in linux package in Ubuntu: Confirmed Bug description: This is an issue I faced before #1899304 but becomes more critical with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304 The big concern is that if AGP is disabled, there is no fallback display option on those platforms. After having discovered some K8 and K10 computers running AGP cards stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to try some PCI cards to know if problems came from AGP or something else, and I've discovered another issue instead. Note that I'm not talking about PCI express, but good old PCI. The other issue I found is that PCI graphics on AMD K8/K10 platform is broken since years. This got probably unnoticed because such hardware works on Intel platform and those cards are not very common, so the chance to fulfill all the requirements to reproduce the bug are not that high. To make the test significant enough I used two PCI devices from two makers, and some that are not so old: they both support OpenGL 3.3, have 512MB of VRAM, and one of them even have HDMI. - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA I've driven tests on four computers: - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI Both PCI GPU work on the Intel based computer, and I get performances that looks correct for those GPU given they are PCI ones. You can find real-life use case test result here (look for “PCI”): https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix I tested two Ubuntu versions and multiple kernels: Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic All those configurations fail with those two PCI GPUs on AMD K8/K10 platforms. I got some logs and screenshots, so I will add them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Hey there, according to the above statements there has been a fix released for bluez bluetooth stack as well for ubuntu system? Am I able to get this fix installed for now? Best Regards Dennis -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902795] Re: PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1
I've reproduced the issue on Piledriver platform with AMD 9590 CPU, with both ATI and Nvidia PCI GPUs. With the ATI GPU, I get the usual symptom of the computer freezing display while the GNOME desktop is partially loaded. It's possible to open a TTY console by switching consoles but once returned to the graphical desktop, the computer becomes definitely unresponsive. This is similar to what is seen on older hardware like K10 or K8 platforms. With the Nvidia GPUs, I get garbage (we can even notice some parts of the GNOME desktop), and the computer is unresponsive. Sometime the display is lost then returns and it cycles like that. This is the usual symptom seen on older hardware like K10 and K8 platforms. ** Attachment added: "Screenshot of graphical issues on Nvidia Geforce 8400GS rev.2 PCI on Piledriver PCIe host" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+attachment/5432604/+files/20201109-110741-000.nvidia-geforce-8400gsr2-pci+piledriver.jpg ** Summary changed: - PCI graphics broken on AMD K8/K10 platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 + PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902795 Title: PCI graphics broken on AMD K8/K10/Piledriver platform (while it works on Intel) verified from Linux 4.4 to 5.10-rc1 Status in linux package in Ubuntu: Confirmed Bug description: This is an issue I faced before #1899304 but becomes more critical with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899304 The big concern is that if AGP is disabled, there is no fallback display option on those platforms. After having discovered some K8 and K10 computers running AGP cards stopped working with 5.4.0-48 (Ubuntu 20.04 LTS), I had the idea to try some PCI cards to know if problems came from AGP or something else, and I've discovered another issue instead. Note that I'm not talking about PCI express, but good old PCI. The other issue I found is that PCI graphics on AMD K8/K10 platform is broken since years. This got probably unnoticed because such hardware works on Intel platform and those cards are not very common, so the chance to fulfill all the requirements to reproduce the bug are not that high. To make the test significant enough I used two PCI devices from two makers, and some that are not so old: they both support OpenGL 3.3, have 512MB of VRAM, and one of them even have HDMI. - PCI ATI Radeon HD 4350 (RV710, Terascale 1), HDMI + DVI-I + VGA - PCI Nvidia Geforce 8400 GS rev.2 (NV98, Tesla 1.0), DVI-I + VGA I've driven tests on four computers: - K10 PCIe based: Dell Optiplex 740 motherboard with AMD Athlon 64 X2 CPU (dual core), Nvidia C51 bridge, 6GB DDR2 667MHz, PCIe + PCI - K8 AGP based: ASRock AM2NF3-VSTA motherboard with AMD Phenom II X4 970 CPU (quad core), Nvidia nForce3 bridge, 16GB DDR2 800MHz, AGP + PCI - K8 AGP based: MSI MS-6702E motherboard with AMD Athlon 64 3200+ CPU (single core), VIA K8T800Pro, VT8237/8251 bridge, 3GB DDR 400MHz, AGP + PCI - Intel PCIe based: Lenovo ThinkCentre M58 motherboard with Pentium E5200 CPU (dual core), Intel 82801 PCI Bridge, 1GB DDR2 800MHz, PCIe + PCI Both PCI GPU work on the Intel based computer, and I get performances that looks correct for those GPU given they are PCI ones. You can find real-life use case test result here (look for “PCI”): https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix I tested two Ubuntu versions and multiple kernels: Ubuntu 20.04 Focal LTS Linux 5.4.0-48-generic Ubuntu 20.04 Focal LTS Linux 5.4.0-47-generic Ubuntu 16.04 Xenial LTS Linux 4.15.0-118-generic Ubuntu 16.04 Xenial LTS Linux 4.8.0-36-generic Ubuntu 16.04 Xenial LTS Linux 4.4.0-190-generic All those configurations fail with those two PCI GPUs on AMD K8/K10 platforms. I got some logs and screenshots, so I will add them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot
** Changed in: linux Status: Confirmed => 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/1848445 Title: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot Status in Linux: Expired Status in linux package in Ubuntu: Triaged Bug description: When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops with just a non-blinking white cursor on screen in the top left, and the Caps Lock doesn't respond when pressed. Previously on 4.x kernels, system would boot using acpi=off argument creating more problems. WORKAROUND: Boot with kernel parameter: acpi_osi= 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: wl ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ilgaz 21270 F pulseaudio /dev/snd/controlC1: ilgaz 21270 F pulseaudio /dev/snd/pcmC1D0p: ilgaz 21270 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 10:02:44 2019 HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae InstallationDate: Installed on 2019-10-13 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Hewlett-Packard HP Pavilion 13 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi= 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: Upgraded to eoan on 2019-10-16 (0 days ago) dmi.bios.date: 06/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.41 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2341 dmi.board.vendor: Hewlett-Packard dmi.board.version: 07.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 13 x360 PC dmi.product.sku: L0B89EA#AB8 dmi.product.version: 097712405F0410180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1848445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902420] Re: WiFi connection extremely slow
Hello, After installing the kernel and patches, my WiFi speed fluctuates up and down. When it's up it does reach the expected speed but then it drops to a couple of Kbps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902420 Title: WiFi connection extremely slow Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 20.04 on dual boot with Windows 10. WiFi works fine on Windows 10 but it gets extremely slow on Ubuntu. I tried every solution online, from disabling 802.11n protocol to reinstalling the RTL8723DE driver, and nothing worked. My system running on Legacy BIOS if that helps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl 8723de ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anas 2021 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 12:59:12 2020 InstallationDate: Installed on 2020-08-26 (66 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 002: ID 04f2:b5d5 Chicony Electronics Co., Ltd HP TrueVision HD Camera Bus 001 Device 005: ID 18d1:4ee3 Google Inc. Nexus 4/5/7/10 (tether) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-bp0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=42b4fac6-3794-423f-9ce0-d84b68f0d802 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-10-31 (0 days ago) dmi.bios.date: 04/06/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8360 dmi.board.vendor: HP dmi.board.version: 46.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd04/06/2017:svnHP:pnHPLaptop14-bp0xx:pvrType1ProductConfigId:rvnHP:rn8360:rvr46.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-bp0xx dmi.product.sku: 1WA11EA#A2N dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
After setting core.default_ps_max_latency_us=200 and running for a few hours, the system slows down significantly with intermittent long pauses. As all of this is rendering my computer unusable for work, can somebody advise how to restore an use a previous kernel (and which one)? Thanks and much appreciated! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Confirmed Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by
[Kernel-packages] [Bug 1766300] Re: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist
@ebonato in focal, the service fails because of that condition: $ systemctl status hv-fcopy-daemon.service ● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at Mon 2020-11-09 10:03:59 UTC; 58s ago └─ ConditionPathExists=/dev/vmbus/hv_fcopy was not met any advise? -- 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/1766300 Title: hv-fcopy-daemon service fails to start if /dev/vmbus/hv_fcopy doesn't exist Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Trusty: New Status in linux-azure source package in Trusty: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Artful: New Status in linux-azure source package in Artful: New Status in linux source package in Bionic: Incomplete Status in linux-azure source package in Bionic: New Bug description: On VMs launched in Azure, /dev/vmbus/hv_fcopy doesn't exist, so hv- fcopy-daemon fails to start. This means that boot is degraded by default: $ systemctl list-units --failed --no-legend hv-fcopy-daemon.service loaded failed failed Hyper-V File Copy Protocol Daemon $ systemctl is-system-running degraded which makes detecting other failures much harder to automate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-cloud-tools-common 4.15.0-15.16 ProcVersionSignature: User Name 4.15.0-1004.4-azure 4.15.15 Uname: Linux 4.15.0-1004-azure x86_64 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-0ubuntu6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A Date: Mon Apr 23 16:27:47 2018 Dependencies: IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1004-azure root=UUID=fda9466a-9068-447f-8572-6d8d310eabd3 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 RelatedPackageVersions: linux-restricted-modules-4.15.0-1004-azure N/A linux-backports-modules-4.15.0-1004-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 44FD5ABF-DE16-AD4A-B2E0-6E70167950AF dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: coreutils (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in coreutils source package in Focal: Confirmed Status in zfs-linux source package in Focal: Triaged Status in zsys source package in Focal: Confirmed Status in coreutils source package in Groovy: Confirmed Status in zfs-linux source package in Groovy: Triaged Status in zsys source package in Groovy: Confirmed Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zsys (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in coreutils source package in Focal: Confirmed Status in zfs-linux source package in Focal: Triaged Status in zsys source package in Focal: Confirmed Status in coreutils source package in Groovy: Confirmed Status in zfs-linux source package in Groovy: Triaged Status in zsys source package in Groovy: Confirmed Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zsys (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in coreutils source package in Focal: Confirmed Status in zfs-linux source package in Focal: Triaged Status in zsys source package in Focal: Confirmed Status in coreutils source package in Groovy: Confirmed Status in zfs-linux source package in Groovy: Triaged Status in zsys source package in Groovy: Confirmed Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Changed in: zfs-linux (Ubuntu) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu) Status: Triaged => In Progress ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Also affects: coreutils (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: zsys (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: coreutils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: zsys (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Focal) Status: New => Triaged ** Changed in: zfs-linux (Ubuntu Groovy) Status: New => Triaged ** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu Groovy) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu Focal) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) ** Changed in: zfs-linux (Ubuntu Groovy) Assignee: (unassigned) => Jean-Baptiste Lallement (jibel) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in coreutils source package in Focal: Confirmed Status in zfs-linux source package in Focal: Triaged Status in zsys source package in Focal: Confirmed Status in coreutils source package in Groovy: Confirmed Status in zfs-linux source package in Groovy: Triaged Status in zsys source package in Groovy: Confirmed Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: coreutils (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1894329 Title: ZFS revert from grub menu not working. Status in coreutils package in Ubuntu: Incomplete Status in zfs-linux package in Ubuntu: In Progress Status in zsys package in Ubuntu: Invalid Status in coreutils source package in Focal: Confirmed Status in zfs-linux source package in Focal: Triaged Status in zsys source package in Focal: Confirmed Status in coreutils source package in Groovy: Confirmed Status in zfs-linux source package in Groovy: Triaged Status in zsys source package in Groovy: Confirmed Bug description: @coreutils maintainers, any idea why dd is being flagged as having an executable stack? When I try to revert to a previous state from the grub menu, the boot fails. The system drops me to a repair modus. zfs-mount-generator fails with the message: couldn't ensure boot: Mounted clone bootFS dataset created by initramfs doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"". After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed without a suffix. After a little investigation I found the problem in /usr/share/initramfs-tools/scripts/zfs at the end in function uid() { dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 }, the dd command fails during boot with the message "process 'dd' started with executable stack. After this an empty uid is returned which explains the dataset without a proper suffix. Replacing the function with: uid() { grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6 } fixes the problem. Ubuntu version is: Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 zfs-initramfs version is: 0.8.4-1ubuntu11 With regards, Usarin Heininga ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: zfs-initramfs 0.8.4-1ubuntu11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 4 20:23:44 2020 InstallationDate: Installed on 2020-09-02 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900883] Re: Add new iwlwifi firmware to solve AX201 hang
This bug was fixed in the package linux-firmware - 1.187.4 --- linux-firmware (1.187.4) focal; urgency=medium * Add new iwlwifi firmware to fix AX201 hang (LP: #1900883) - UBUNTU: SAUCE: Add iwlwifi-QuZ-a0-hr-b0-50.ucode * Fix broken Realtek 8821C BT after S3 (LP: #1901129) - rtl_bt: Update RTL8821C BT FW to 0xAA6C_A99E -- Seth Forshee Wed, 28 Oct 2020 16:05:46 -0500 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900883 Title: Add new iwlwifi firmware to solve AX201 hang Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Intel AX201 firmware crashes or hardware RX ring buffer hangs after S3. [Fix] Use new firmware from linux-firmware.git can solve the issue. [Test] WiFi works for each cycle of 1000 S3 cycles. [Regression Potential] Both Focal 5.4 and OEM 5.6 kernel use this firmware, so it might regress current 5.4 users. I did a smoke test with this firmware on Focal 5.4, and I didn't see any regression. Instead of cherry-pick the commit, only add the firmware needed for AX201 to minimize the regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901129] Re: Fix broken Realtek 8821C BT after S3
This bug was fixed in the package linux-firmware - 1.187.4 --- linux-firmware (1.187.4) focal; urgency=medium * Add new iwlwifi firmware to fix AX201 hang (LP: #1900883) - UBUNTU: SAUCE: Add iwlwifi-QuZ-a0-hr-b0-50.ucode * Fix broken Realtek 8821C BT after S3 (LP: #1901129) - rtl_bt: Update RTL8821C BT FW to 0xAA6C_A99E -- Seth Forshee Wed, 28 Oct 2020 16:05:46 -0500 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1901129 Title: Fix broken Realtek 8821C BT after S3 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] Realtek 8821C Bluetooth controller may stop working after S3. [Fix] Use the new firmware from Realtek (Release Version: 0xAA6C_A99E) Link: https://lore.kernel.org/linux-firmware/20201013084718.3077-1-max.c...@realtek.com/ [Test] With the new firmware, the BT controller works and can pass 1000 cycles of S3. [Regression Potential] This is tested with some BT devices, no regressions found so far. However, regression could still happen because there are many Bluetooth peripherals we can't test. We'll escalate the issue to Realtek if regression ever happens. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900883] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1900883 Title: Add new iwlwifi firmware to solve AX201 hang Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Intel AX201 firmware crashes or hardware RX ring buffer hangs after S3. [Fix] Use new firmware from linux-firmware.git can solve the issue. [Test] WiFi works for each cycle of 1000 S3 cycles. [Regression Potential] Both Focal 5.4 and OEM 5.6 kernel use this firmware, so it might regress current 5.4 users. I did a smoke test with this firmware on Focal 5.4, and I didn't see any regression. Instead of cherry-pick the commit, only add the firmware needed for AX201 to minimize the regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901129] Re: Fix broken Realtek 8821C BT after S3
This bug was fixed in the package linux-firmware - 1.190.1 --- linux-firmware (1.190.1) groovy; urgency=medium * Fix broken Realtek 8821C BT after S3 (LP: #1901129) - rtl_bt: Update RTL8821C BT FW to 0xAA6C_A99E -- Seth Forshee Wed, 28 Oct 2020 15:51:48 -0500 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1901129 Title: Fix broken Realtek 8821C BT after S3 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] Realtek 8821C Bluetooth controller may stop working after S3. [Fix] Use the new firmware from Realtek (Release Version: 0xAA6C_A99E) Link: https://lore.kernel.org/linux-firmware/20201013084718.3077-1-max.c...@realtek.com/ [Test] With the new firmware, the BT controller works and can pass 1000 cycles of S3. [Regression Potential] This is tested with some BT devices, no regressions found so far. However, regression could still happen because there are many Bluetooth peripherals we can't test. We'll escalate the issue to Realtek if regression ever happens. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901129] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1901129 Title: Fix broken Realtek 8821C BT after S3 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] Realtek 8821C Bluetooth controller may stop working after S3. [Fix] Use the new firmware from Realtek (Release Version: 0xAA6C_A99E) Link: https://lore.kernel.org/linux-firmware/20201013084718.3077-1-max.c...@realtek.com/ [Test] With the new firmware, the BT controller works and can pass 1000 cycles of S3. [Regression Potential] This is tested with some BT devices, no regressions found so far. However, regression could still happen because there are many Bluetooth peripherals we can't test. We'll escalate the issue to Realtek if regression ever happens. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
Hello, do you still seeing this issue with the latest kernel on you system? Thanks ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-hwe-edge (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
I am closing this bug as this issue seems to be fixed. Please file a new bug if you're still experiencing this issue. Thanks. ** Changed in: linux-hwe (Ubuntu) Status: Confirmed => Invalid ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I upgraded from 16.04 to 18.04 (from kernel 4.4.0-193-generic to 4.15.0-122-generic) and I had this exact issue. Same HP Microserver Gen 8 as the others, probably there's something in their motherboard that makes SATA disks discovery particularly slow, and the kernel (or initrd scripts harness?) doesn't _really_ wait for /dev to populate properly. Doesn't seem fixed in next kernels, or at least not in what is available on 18.04 - I installed the HWE kernel (5.4.0-52-generic) and I have the problem just the same; the only thing that fixed it was the "sleep" workaround before "/bin/btrfs device scan". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: See attached dmesg outputs for booting kernels 4.11.x (working) and 4.13.x (not working). dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x. btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have been discovered by the kernel. The btrfs RAID1 filesystem mounts, and everything is good. dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x. btrfs scans for devices after only 2 (sda, sdb) of the devices have been discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed to read the system array: -5"). The remaining 2 devices (sdc, sdd) are discovered by the kernel immediately afterward. At the end of the log, I run `btrfs device scan` and mount the filesystem manually. Hardware: HP ProLiant MicroServer Gen8 4x WDC WD20EFRX --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: aplay: device_list:270: no soundcards found... ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: arecord: device_list:270: no soundcards found... DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-10-15 (933 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: HP ProLiant MicroServer Gen8 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ rootdelay=10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/16/2015 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load
If you can ran a full cycle of bonnie++ then I doubt it's caused by SSD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Incomplete Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load
Here come the results: guillaume@massada:~$ bonnie++ Writing a byte at a time...done Writing intelligently...done Rewriting...done Reading a byte at a time...done Reading intelligently...done start 'em...done...done...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.98 --Sequential Output-- --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Name:Size etc/sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP massada 15696M 535k 98 28.7m 4 14.5m 8 1367k 99 29.6m 9 3454 103 Latency 21555us 38143ms 23634ms 11250us 15695us 10672us Version 1.98 --Sequential Create-- Random Create massada -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 0 26 + +++ + +++ 724249376 33 + +++ + +++ Latency 14815us1195us 293us 680us 25us 855us 1.98,1.98,massada,1,1604871797,15696M,,8192,5,535,98,29346,4,14870,8,1367,99,30277,9,3454,103,16,18820,26,+,+++,+,+++,32166,33,+,+++,+,+++,21555us,38143ms,23634ms,11250us,15695us,10672us,14815us,1195us,293us,680us,25us,855us The problem definitely occurred using bonnie++, from the "Writing intelligently" phase ownards : e.g. opening a new tab in the Gnome Terminal did not work and a "Terminal is not responding" window appeared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Incomplete Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd
[Kernel-packages] [Bug 1858463] Re: Desktop freezing while SSD under heavy load
bonnie++ results ** Attachment added: "Capture d’écran de 2020-11-09 09-02-13.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858463/+attachment/5432558/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-11-09%2009-02-13.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Incomplete Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation