[Kernel-packages] [Bug 1888779] 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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: Confirmed Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395456/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395462/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395455/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395459/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395465/+files/WifiSyslog.txt ** 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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395460/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395457/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395458/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395450/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395464/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395453/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395461/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395463/+files/RfKill.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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395449/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395452/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395451/+files/IwConfig.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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395454/+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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*
apport information ** Tags added: apport-collected focal ** Description changed: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: andrei 2258 F pulseaudio + /dev/snd/controlC1: andrei 2258 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 + DistroRelease: KDE neon 20.04 + HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab + InstallationDate: Installed on 2017-12-26 (940 days ago) + InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 + MachineType: Dell Inc. Inspiron 5570 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-51-generic N/A + linux-backports-modules-5.3.0-51-generic N/A + linux-firmware1.187.1 + Tags: focal + Uname: Linux 5.3.0-51-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 09/08/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.0.4 + dmi.board.name: 0DRPKR + dmi.board.vendor: Dell Inc. + dmi.board.version: X07 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5570 + dmi.product.sku: 0810 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1888779/+attachment/5395448/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture:
[Kernel-packages] [Bug 1888779] 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 1888779 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: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: Incomplete Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859873] Re: Reapply "usb: handle warm-reset port requests on hub resume"
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859873 Title: Reapply "usb: handle warm-reset port requests on hub resume" Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1859873 [Impact] We wish to reapply "usb: handle warm-reset port requests on hub resume". We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a perceived regression it introduced (bug 1856608). Only one customer saw this regression, and only in very specific systems. We have now determined that the root cause of the regression was that the systems used defective USB cables, which had Tx and Rx lines mixed up. Signals were being sent down the wrong wires, placing the USB devices into a SS_INVALID link state, and this patch simply revealed the problems going on in the USB3 subsystem. USB3 devices never worked with these cables, but for some reason USB2 worked, which led to the long drawn out debugging timeframe. We have confirmation from device hardware teams that USB cables on affected systems have their Tx and Rx wires mixed up, and this has also been confirmed by the USB cable manufacturer that these cables are a bad batch. New USB cables fix the problem, and "usb: handle warm-reset port requests on hub resume" is safe to reapply. [Fix] We reapply upstream commit: commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e Author: Jan-Marek Glogowski Date: Fri Feb 1 13:52:31 2019 +0100 Subject: usb: handle warm-reset port requests on hub resume To the Bionic and Eoan kernels. This commit fixes a real problem for users of a particular external hard disk, so it has value for Ubuntu users, and we do not want to diverge from upstream stable patches. [Testcase] For users with defective non-complaint USB cables: dmesg | grep "Cannot enable" For users with a particular USB-C external hard disk: The disk will work as expected when it is plugged in. [Regression Potential] If any users in the community happen to use USB cables with Tx and Rx lines mixed up, they may see messages like: "usb usb2-port2: Cannot enable. Maybe the USB cable is bad?" These users need to swap out their USB cables for a non-defective one. The commit landed in 5.1, and was backported to all stable kernels. As of 5.8-rc6, the commit is still in place, and has no fixup commits. I believe that re-introducing this commit will not cause any regressions for users with USB compliant hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] [NEW] Can't boot with Linux 5.4.0.*
Public bug reported: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of "sudo lspci -vnvn"" https://bugs.launchpad.net/bugs/1888779/+attachment/5395432/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: New Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
I have had this issue with my C270 on Windows and now on Ubuntu 20.04. So it's mainly a Logitech issue, but on Windows I fixed it by fixing the mic on 16000 hz. On Ubuntu I tried chaging etc/pulse/daemon.conf to ; default-sample-rate = 16000 ; alternate-sample-rate = 16000 and it did not work. Only for a little while. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Oneiric: Fix Released Status in linux package in Debian: New Bug description: Did not know which application to log so feel free to let me know and I'll upload the correct log. In Natty, this mic worked great. Now, in the sound control panel, the mic does not show any input level at all and sound recorder does not record any sound. edit: I can also confirm the same behavior as Alex Popovskiy. It either works but plays too fast (high pitch) or it doesn't work at all. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Sep 6 20:31:13 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alex 1594 F pulseaudio /dev/snd/controlC0: alex 1594 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,18490397,0010' Controls : 36 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0809' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 6400 Mono: Capture 6400 [100%] [31.00dB] [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-10-generic N/A linux-backports-modules-3.0.0-10-generic N/A linux-firmware1.60 Tags: oneiric running-unity Uname: Linux 3.0.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: M3A770DE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879575] Re: rtl8822be not initialized: rtw_pci: Refused to change power state, currently in D3
[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/1879575 Title: rtl8822be not initialized: rtw_pci: Refused to change power state, currently in D3 Status in linux package in Ubuntu: Expired Bug description: Wifi adapter can't find avaiable connections in new kernel. Upgraded from 19.04 to 19.10 and then to 20.04 on Lenovo Legion y530 which comes with realtek wifi adapter. lspci shows the pci adapter but not found in lshw -C network. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manish 1950 F pulseaudio /dev/snd/controlC0: manish 1950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-06 (318 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=a67f2402-8ada-4a31-8500-4ce7031521e2 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
[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/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Expired Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_add_reference +4,89% 0,07% kworker/0:1+kac [kernel.kallsyms]
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.
Issue found on B-5.3 generic kernel with google cloud (didn't see this issue with other gcp / gke cloud kernels) ** Summary changed: - fib related test in net from ubuntu_kernel_selftests failed + fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. ** Tags added: sru-20200629 ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux-aws (Ubuntu Disco) ** No longer affects: linux-kvm (Ubuntu Disco) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Status in linux-kvm source package in Eoan: New Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880519] Re: System stops responding while entering S3 with SD card installed
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880519 Title: System stops responding while entering S3 with SD card installed Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Won't Fix Status in linux-oem source package in Eoan: Invalid Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: Triaged Status in linux-oem source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [SRU Justfication] [Impact] The system stops responding while entering S3, screen will be lit up if touchpad is triggered by finger. Cursor could be seen with black background, but system is not responding to any input. [Fix] b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM f0c472a6da51 xhci: Return if xHCI doesn't support LPM [Fix] Patchset[1] for fix this issue currently landed in upstream, so we backported them: [1]: b3d71abd135e xhci: Poll for U0 after disabling USB2 LPM f0c472a6da51 xhci: Return if xHCI doesn't support LPM [Test] With the above patch applied, run: sudo fwts --s3-sleep-delay=30 --s3-multiple=30 -p s3 Can passed 30 times. [Regression Potential] Low, the patch is just like a safeguard, doesn't really change any behavior. [Reproduce Steps] 1. Install dell-bto-bionic-bolt-l-X51-20190720-56.iso 2. Upgrade kernel to 4.15.0-1080-oem 3. Boot the system with 4.15.0-1080-oem kernel 4. Insert SD card 5. Suspend the system to S3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1888647] Re: Realtek wifi dont work after update
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Triaged -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Triaged Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel
[Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install
"nomodeset" will disable all hardware graphics support so it will use high CPU and likely cause screen tearing. That's not really a solution so you should remove "nomodeset" as soon as you can. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859873] Re: Reapply "usb: handle warm-reset port requests on hub resume"
** Description changed: - This bug tracks the reapplication of "usb: handle warm-reset port - requests on hub resume". + [Impact] + + We wish to reapply "usb: handle warm-reset port requests on hub resume". We reverted "usb: handle warm-reset port requests on hub resume" from - the Ubuntu kernels due to a regression it introduced (bug 1856608). - However, that patch did fix an issue for a user, and reverting it - requires us to diverge from mainline. Once we understand and resolve the - regression, we should reapply it. + the Ubuntu kernels due to a perceived regression it introduced (bug + 1856608). + + Only one customer saw this regression, and only in very specific + systems. We have now determined that the root cause of the regression + was that the systems used defective USB cables, which had Tx and Rx + lines mixed up. + + Signals were being sent down the wrong wires, placing the USB devices + into a SS_INVALID link state, and this patch simply revealed the + problems going on in the USB3 subsystem. USB3 devices never worked with + these cables, but for some reason USB2 worked, which led to the long + drawn out debugging timeframe. + + We have confirmation from device hardware teams that USB cables on + affected systems have their Tx and Rx wires mixed up, and this has also + been confirmed by the USB cable manufacturer that these cables are a bad + batch. + + New USB cables fix the problem, and "usb: handle warm-reset port + requests on hub resume" is safe to reapply. + + [Fix] + + We reapply upstream commit: + + commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e + Author: Jan-Marek Glogowski + Date: Fri Feb 1 13:52:31 2019 +0100 + Subject: usb: handle warm-reset port requests on hub resume + + To the Bionic and Eoan kernels. + + This commit fixes a real problem for users of a particular external hard + disk, so it has value for Ubuntu users, and we do not want to diverge + from upstream stable patches. + + [Testcase] + + For users with defective non-complaint USB cables: + + dmesg | grep "Cannot enable" + + For users with a particular USB-C external hard disk: + + The disk will work as expected when it is plugged in. + + [Regression Potential] + + If any users in the community happen to use USB cables with Tx and Rx + lines mixed up, they may see messages like: + + "usb usb2-port2: Cannot enable. Maybe the USB cable is bad?" + + These users need to swap out their USB cables for a non-defective one. + + The commit landed in 5.1, and was backported to all stable kernels. As + of 5.8-rc6, the commit is still in place, and has no fixup commits. I + believe that re-introducing this commit will not cause any regressions + for users with USB compliant hardware. ** Description changed: + BugLink: https://bugs.launchpad.net/bugs/1859873 + [Impact] We wish to reapply "usb: handle warm-reset port requests on hub resume". We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a perceived regression it introduced (bug 1856608). Only one customer saw this regression, and only in very specific systems. We have now determined that the root cause of the regression was that the systems used defective USB cables, which had Tx and Rx lines mixed up. Signals were being sent down the wrong wires, placing the USB devices into a SS_INVALID link state, and this patch simply revealed the problems going on in the USB3 subsystem. USB3 devices never worked with these cables, but for some reason USB2 worked, which led to the long drawn out debugging timeframe. We have confirmation from device hardware teams that USB cables on affected systems have their Tx and Rx wires mixed up, and this has also been confirmed by the USB cable manufacturer that these cables are a bad batch. New USB cables fix the problem, and "usb: handle warm-reset port requests on hub resume" is safe to reapply. [Fix] We reapply upstream commit: commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e Author: Jan-Marek Glogowski Date: Fri Feb 1 13:52:31 2019 +0100 Subject: usb: handle warm-reset port requests on hub resume To the Bionic and Eoan kernels. This commit fixes a real problem for users of a particular external hard disk, so it has value for Ubuntu users, and we do not want to diverge from upstream stable patches. [Testcase] For users with defective non-complaint USB cables: dmesg | grep "Cannot enable" For users with a particular USB-C external hard disk: The disk will work as expected when it is plugged in. [Regression Potential] If any users in the community happen to use USB cables with Tx and Rx lines mixed up, they may see messages like: "usb usb2-port2: Cannot enable. Maybe the USB cable is bad?" These users need to swap out their USB cables for a non-defective one. The commit landed in 5.1, and was backported to all stable kernels. As
[Kernel-packages] [Bug 1859873] Re: Reapply "usb: handle warm-reset port requests on hub resume"
** No longer affects: linux (Ubuntu Focal) ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859873 Title: Reapply "usb: handle warm-reset port requests on hub resume" Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: In Progress Bug description: This bug tracks the reapplication of "usb: handle warm-reset port requests on hub resume". We reverted "usb: handle warm-reset port requests on hub resume" from the Ubuntu kernels due to a regression it introduced (bug 1856608). However, that patch did fix an issue for a user, and reverting it requires us to diverge from mainline. Once we understand and resolve the regression, we should reapply it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
Attached is a procps debdiff for groovy, which adds documentation to /etc/sysctl.d/10-kernel-hardening.conf and a commented out way to disable DMESG_RESTRICT. ** Patch added: "procps debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395388/+files/lp1886112_procps_groovy.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by changing kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf from '1' to '0', followed by a reboot.
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
Attached is a debdiff for util-linux which implements the permission and capability changes to the dmesg binary. ** Patch added: "util-linux debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+attachment/5395389/+files/lp1886112_util-linux_groovy.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by changing kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf from '1' to '0', followed by a reboot. To manage notifications about this bug
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
I emailed Seth Forshee asking about what happens when Groovy's kernel becomes Focal's HWE kernel, and he mentioned that the kernel team has processes in place to handle config changes, and that it isn't a problem. So we will go with the more secure by default way, and enable CONFIG_SECURITY_DMESG_RESTRICT in the kernel config. I rebased the patches for procps and util-linux to the latest versions in groovy and their debdiffs are attached below. Since things are quiet on this bug I will write to ubuntu-devel shortly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) Add kernel.dmesg_restrict = 1 to /etc/sysctl.d/10-kernel-hardening.conf 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hi, my pc has been on win10 for months. Was on VM a couple of month until I got really tired of maintaining 2 setups so I deleted my VM and now deperately waiting for a fix because I have projects that require linux. Please help us. Windows is not better than linux but if in this case, 8 months without a working ouchpads is like being set back 30 years. Please keep us posted. -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend
For the previous post I am the author of Bug #1887202, which is considered a duplicate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867983 Title: Computer is frozen after suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Confirmed Bug description: === SRU Justification === [Impact] Some systems with ATA drives freeze during suspend [Fix] Avoid circular sync dependency by using async cookie. [Test] User reports positive feedback. [Regression Potential] Low. This patch makes synchronize more targeted, prevents many potential freeze. === Original Bug Report === I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" 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=/boot/vmlinuz-5.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend
I am unable to try the updates at deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe. They are rejected with this: The repository 'http://archive.ubuntu.com/ubuntu $(lsb_release Release' does not have a Release file.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.The repository 'http://ports.ubuntu.com/ubuntu-ports $(lsb_release Release' does not have a Release file. I tried the latest 5.4.0-42 and still have issue. I am not a Linux wiz and cannot resolve the above error in the repository, but the bug still exists. It should not be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867983 Title: Computer is frozen after suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Confirmed Bug description: === SRU Justification === [Impact] Some systems with ATA drives freeze during suspend [Fix] Avoid circular sync dependency by using async cookie. [Test] User reports positive feedback. [Regression Potential] Low. This patch makes synchronize more targeted, prevents many potential freeze. === Original Bug Report === I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" 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=/boot/vmlinuz-5.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
New to the thread, HP envy, ryzen 4500. Running 5.7.10, Mint 20. Had the same issues as everyone else, sleep with lid wont allow it to wake, but oddly if I manually suspend, it comes back fine. Tried fix #54 and it did seem to fix my issues, thank you khitschler. I dont have any screen tearing or any artifacts in 4k videos. So I might be lucky, it's a decent fix for me. I'll keep an eye on the thread to see if a better fix comes out, not sure what EnablePageFlip actually does for my laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing
Thank you Pierre for the solution. I had the same problem and tried everything. Lost a lot of time on this stupid problem. I cannot believe this is happening in Ubuntu in 2020. This kind of BS keeps me from recommending Linux to regular computer users! -- 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/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: Invalid Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5
Chime in on this email thread if interested: https://lore.kernel.org/r/20200723201403.GA1450503@bjorn-Precision-5520 There are instructions at the bottom of that page about how to reply to the thread. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5
** Summary changed: - touchpad doesn't work at all on ACER Spin 5 + touchpad and touchscreen doesn't work at all on ACER Spin 5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad and touchscreen doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
It seems we got stuck here, I've done everything I was asked for, now we
need somebody kernel-competent to review what I've posted and... let's
hope it will not take too long. If anybody else is affected, please mark
so at the top ("this affects me too") - to give this bug more heat
points. Thanks a lot to everyone involved!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad doesn't work at all on ACER Spin 5
Status in linux package in Ubuntu:
Confirmed
Bug description:
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
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=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
I've not updated and got this error at random while playing a 3D game. (Never had this crash before in the 6 months I've been using this driver) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects
@Dimitri Thx, that update is helpful (we briefly touched on that today). Before that, the know status for me was like at the end of comment #1. I wasn't aware of any activity, nor progress, since the status was still Triaged. Glad to hear that you and/or the kernel team already pushed this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk: root@t35lp25:/~# apt install zfcpdump-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: zfcpdump-kernel 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 1655 kB of archives. After this operation, 1757 kB of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB] Fetched 1655 kB in 1s (1803 kB/s) Selecting previously unselected package zfcpdump-kernel. (Reading database ... 53866 files and directories currently installed.) Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ... Unpacking zfcpdump-kernel (4.13-0ubuntu1) ... Setting up zfcpdump-kernel (4.13-0ubuntu1) ... root@t35lp25:/~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for partition dump: No such file or directory root@t35lp25:~# ls /lib/s390-tools/zfcpdump/ zfcpdump-initrd zfcpdump_part.image root@t35lp25:~# As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is available. with paramater -d, zipl does NOT accept -i to override the image name. Thus I renamed zfcpdump_part.image to zfcpdump-image: root@t35lp25:~# cd /lib/s390-tools/zfcpdump root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 cgroup_disable=memory ' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x001b9fff parmline: 0x001ba000-0x001ba1ff initial ramdisk.: 0x001c-0x0020edff Preparing boot device: sde. Done. root@t35lp25:/lib/s390-tools/zfcpdump# === Hi, zfcpdump_part.image got renamed to zfcpdump-image upstream with s390-tools v2.7.0. For me it looks like the old name is hard coded somewhere in the packaging/installation routines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Given it's probably not going to happen to you again (since it was an upgrade glitch), are you OK if we close this bug? -- 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/1849981 Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Incomplete Bug description: Was upgrading to 19.10 and encountered this ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfs-dkms 0.8.1-1ubuntu14 ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 10:28:20 2019 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2013-06-08 (2331 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
OK. I fully understand your concerns with sharing that information. Normally this issue occurs if you have the zfs-dkms modules installed - these are no longer required so you can safely remove zfs-dkms if you haven't done so already. I was suspecting that some dkms dependency (such as a tool chain or specific kernel headers were missing or some gcc issue) was causing this issue. -- 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/1849981 Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Incomplete Bug description: Was upgrading to 19.10 and encountered this ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfs-dkms 0.8.1-1ubuntu14 ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 10:28:20 2019 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2013-06-08 (2331 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)
Hey, I own a Notebook 7 and was having the same problem with the headphone jack (sound very low and distorted). I managed to solve based on the solution at https://bbs.archlinux.org/viewtopic.php?pid=1898849#p1898849. Basicaly, I created the files at /lib/firmware/alc256-sound-patch.fw with the content [codec] 0x10ec0256 0x144dc824 0 [verb] 0x1a 0x707 0x05 and at /etc/modprobe.d/alc256-sound-patch.conf with content options snd-hda-intel patch=alc256-sound-patch.fw Reboot, and you should have sound working even after reboots. The values may differ in the codec line, but it's all explained at the link I put. You may test before applying the patch with the command sudo hda-verb /dev/snd/hwC0D0 0x1a 0x707 0x05 (the sound must be playing and headphones connected, but it will no persist after reboot) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850702 Title: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows) Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I can't get sound of my laptop (Samsung Notebook 7 Force) through the headphone jack. The speakers work fine. When I plug a headphone, I can hear the sound being played very faintly. If I bump the volume to the maximum, that is. The sound is very distorted, like a buzz effect being applied over it. I noticed that if I delete /.config/pulse the distortion goes away, but the sound remains very low. After some time, the buzzing effect comes back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Wed Oct 30 16:03:41 2019 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filipe 1294 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-29 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
[Kernel-packages] [Bug 1888695] Re: (Thinkpad L480) Booting hangs at the spinner screen when an HDMI cable is connected to an external monitor
Please try mainline kernels (https://kernel.ubuntu.com/~kernel- ppa/mainline/), for example, 5.8rc6. If it works, please try 5.6 and then repeat bisecting. This can help identify whether fixes are available and what fix is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888695 Title: (Thinkpad L480) Booting hangs at the spinner screen when an HDMI cable is connected to an external monitor Status in linux package in Ubuntu: Confirmed Bug description: Laptop: Lenovo ThinkPad L480 External monitor: Philips 276E8VJSB (4K UHD) Steps to reproduce the problem: 1. While turned off, connect an HDMI cable between the laptop and an external monitor 2. Turn on the laptop 3. Booting hangs at the spinner screen, where it's written "Press Ctrl+C to skip" The laptop boots up normally when the HDMI cable is not connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 16:08:14 2020 InstallationDate: Installed on 2020-04-26 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2113 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LTS01800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a25a653c-6a2a-4954-bd98-bfe2582a2b74 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.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET60W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 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.modalias: dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS01800 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888523] Re: PCIe Bus Error device 8086:a298 spam
Indeed; I was hoping to check what's under the root port just in case, but acknowledge that might not be helpful / have too much stuff under, being a desktop system. Let's see. :) Per the repeated messages I'd imagine this is a device-related error, but wanted to check the kernel version log in case there are related changes there. cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:44
[Kernel-packages] [Bug 1888523] Re: PCIe Bus Error device 8086:a298 spam
The errors comes from physical layer so they likely comes from the root port (00:1d.0) or the device attaches to it. Also, PCIe correctable errors are handled by hardware, so one can turn off some hardware- related features, such as apsm (pcie_aspm=off) or msi (pci=nomsi), to verify whether there are improvement. It is also possible to stop reporting errors via aer (pci=noaer), though this is not recommended. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:44 PC034 kernel: [78387.413811] pcieport :00:1d.0: AER:
[Kernel-packages] [Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects
@frank @ibm this ticket is not helpful, and there is no need for any s390-tools maintainers to comment on. this ticket has been resolved and new name is in use and has been uploaded 3 weeks ago. However, it is not available as it is blocked on manual kernel team review to allow signing of the zfcpdump kernel as requested in a different ticket. This is blocked on review & approval for secureboot signing. ** Changed in: ubuntu-z-systems Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk: root@t35lp25:/~# apt install zfcpdump-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: zfcpdump-kernel 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 1655 kB of archives. After this operation, 1757 kB of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB] Fetched 1655 kB in 1s (1803 kB/s) Selecting previously unselected package zfcpdump-kernel. (Reading database ... 53866 files and directories currently installed.) Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ... Unpacking zfcpdump-kernel (4.13-0ubuntu1) ... Setting up zfcpdump-kernel (4.13-0ubuntu1) ... root@t35lp25:/~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for partition dump: No such file or directory root@t35lp25:~# ls /lib/s390-tools/zfcpdump/ zfcpdump-initrd zfcpdump_part.image root@t35lp25:~# As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is available. with paramater -d, zipl does NOT accept -i to override the image name. Thus I renamed zfcpdump_part.image to zfcpdump-image: root@t35lp25:~# cd /lib/s390-tools/zfcpdump root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 cgroup_disable=memory ' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x001b9fff parmline: 0x001ba000-0x001ba1ff initial ramdisk.: 0x001c-0x0020edff Preparing boot device: sde. Done. root@t35lp25:/lib/s390-tools/zfcpdump# === Hi, zfcpdump_part.image got renamed to zfcpdump-image upstream with s390-tools v2.7.0. For me it looks like the old name is hard coded somewhere in the packaging/installation routines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
It's seems not just one patch can fix this issue. I found another corner case that still can trigger a blutoothd segmentation fault. I pair one Bluetooth keyboard but cancel before input pairing keycode. Before timeout of latest keyboard pairing, I pair another Bluetooth keyboard and still cancel it before input pairing keycode. Please hold this SRU process and I'm debugging for that corner case. ** Changed in: bluez (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: bluez (Ubuntu Bionic) Status: In Progress => Confirmed -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Confirmed Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
So I don't know if this will help or not, but I have troubleshot my P50 turns off on resume from sleep issue. I have Ubuntu on a 2 TB Samsung 970 EVO NVME SSD (with 2B2QEXM7 firmware). If I remove the password (User and Master) from this disk resume from sleep works. I have 2 other Samsung SSDs in the machine (a 1 TB 840 EVO SATA and 1 TB 960 Pro NVME) and I can put passwords on both of them with no problem. Looking on various forums lots of people are reporting sleep/wake issues with the 970 EVO NVME drive. Windows users report that removing the Samsung driver and just using the Windows driver resolves the problems, but I don't know how to change a driver on Ubuntu, or if it's even possible. A Mac user reported that upgrading the drive firmware seemed to fix the problem, but I seem to already be at the latest firmware version. Any tips on how to switch drivers or what to do next would be appreciated. I can run with the drive not password protected, but I don't like it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1888571] Re: Screen flickering and glitching after install
Thanks for the response here. I’ve been using nomodeset which has gotten rid of the flickering as a temporary fix, will modeset do the trick? On Wed, Jul 22, 2020 at 9:35 PM Daniel van Vugt <1888...@bugs.launchpad.net> wrote: > > Intel integrated driver causes screen flickering with Ubuntu install. > > I think you mean the generic 'modeset' driver, which is the correct > driver to use and the one shown in your XorgLog attachments. If you were > using 'xserver-xorg-video-intel' then please just uninstall that > package. It should not be used and commonly causes problems (bug > 1867668). > > Most likely I think this is a kernel bug relating to: > > [ 117.852074] sof-audio-pci :00:1f.3: error: no reply expected, > received 0x0 > [ 117.944970] sof-audio-pci :00:1f.3: firmware boot complete > [ 170.252664] sof-audio-pci :00:1f.3: error: no reply expected, > received 0x0 > [ 170.347691] sof-audio-pci :00:1f.3: firmware boot complete > [ 235.442471] sof-audio-pci :00:1f.3: error: no reply expected, > received 0x0 > [ 235.537670] sof-audio-pci :00:1f.3: firmware boot complete > ... > > > ** Tags added: ice-lake-flicker > > ** Package changed: xorg (Ubuntu) => linux (Ubuntu) > > ** Summary changed: > > - Screen flickering and glitching after install > + [Ice Lake] Screen flickering and glitching after install > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888571 > > Title: > [Ice Lake] Screen flickering and glitching after install > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Intel integrated driver causes screen flickering with Ubuntu install. > Windows did not have this issue > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Jul 22 15:41:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if > 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] > InstallationDate: Installed on 2020-07-22 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: HP HP ENVY Laptop 13-ba0xxx > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/04/2020 > dmi.bios.vendor: Insyde > dmi.bios.version: F.10 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 875A > dmi.board.vendor: HP > dmi.board.version: 07.34 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Envy > dmi.product.name: HP ENVY Laptop 13-ba0xxx > dmi.product.sku: 8KD13AV > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+subscriptions > -- Drew Erikson University of Minnesota - Twin Cities Computer Science & Mathematics | 2020 eriks...@umn.edu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue
[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Hi Sorry I'm not comfortable sharing all my installed packages. I haven't seen this issue since upgrading to 20-04 btw. -- 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/1849981 Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Incomplete Bug description: Was upgrading to 19.10 and encountered this ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfs-dkms 0.8.1-1ubuntu14 ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 10:28:20 2019 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2013-06-08 (2331 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
Just one more information: Befor the bug ocours I had two kernels that gets maintaind by apt: The one without "hwe" and the newer hwe versions. Because the non HWE kernel wasn't used (pulled in via linux-generic). While searching the problem I found that i can remove this non used kernel by doing: apt purge linux-generic linux-headers-generic linux-image-generic linux-modules-nvidia-440-generic Now I had only kernel 5.3.0-61-generic running. The newer ones 5.3.0-62-generic and 5.4* will all result in the mentioned poweroff problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about
[Kernel-packages] [Bug 1888570] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395317/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395321/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395322/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395324/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395315/+files/IwConfig.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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395313/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395318/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395316/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395319/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
I have done as sugested (call apport-collect 1888570). But this was done while running the kernel that works. Should I install the not working kernes and report again ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395325/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
apport information ** Tags added: apport-collected ** Description changed: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: gneiss 1929 F pulseaudio + /dev/snd/controlC0: gneiss 1929 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-05-02 (448 days ago) + InstallationMedia: + + MachineType: Acer Aspire E5-771G + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + LANG=de_DE.UTF-8 + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + PATH=(custom, no user) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee + ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-61-generic N/A + linux-backports-modules-5.3.0-61-generic N/A + linux-firmware1.173.18 + Tags: bionic + Uname: Linux 5.3.0-61-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 09/02/2015 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V1.23 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: EA70_HB + dmi.board.vendor: Acer + dmi.board.version: Type2 - A01 Board Version + dmi.chassis.type: 10 + dmi.chassis.vendor: Chassis Manufacturer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: + dmi.product.family: BDW + dmi.product.name: Aspire E5-771G + dmi.product.sku: Aspire E5-771G_0884_1_23 + dmi.product.version: V3.72 + dmi.sys.vendor: Acer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395312/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh
[Kernel-packages] [Bug 1888570] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395314/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395323/+files/RfKill.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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888570/+attachment/5395320/+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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872383] Re: blk_update_request error when mount nvme partition
https://lkml.org/lkml/2020/7/23/761 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: Precision dmi.product.name: Precision 3930 Rack dmi.product.sku: 0873 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876715] Comment bridged from LTC Bugzilla
--- Comment From jan.hoepp...@de.ibm.com 2020-07-23 11:48 EDT--- (In reply to comment #11) > (In reply to comment #10) > > Hi, were the s390-tools maintainer able to dive deeper into this? > > Hi, > I'm no s390-tools maintainer but I guess in the long run it's easiest when > you rebuild the zfcpdump kernel with the new names otherwise ubuntu will be > decoupled from upstream. Hi, I have to agree with Philipp and the decoupling from upstream. I'd also suggest to rebuild the zfcpdump kernel with the new name. For reference, this is the upstream change that introduced the issue: https://github.com/ibm-s390-tools/s390-tools/commit/724f1fea2c523831a300c71fc67a87f598701846 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk: root@t35lp25:/~# apt install zfcpdump-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: zfcpdump-kernel 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 1655 kB of archives. After this operation, 1757 kB of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB] Fetched 1655 kB in 1s (1803 kB/s) Selecting previously unselected package zfcpdump-kernel. (Reading database ... 53866 files and directories currently installed.) Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ... Unpacking zfcpdump-kernel (4.13-0ubuntu1) ... Setting up zfcpdump-kernel (4.13-0ubuntu1) ... root@t35lp25:/~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for partition dump: No such file or directory root@t35lp25:~# ls /lib/s390-tools/zfcpdump/ zfcpdump-initrd zfcpdump_part.image root@t35lp25:~# As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is available. with paramater -d, zipl does NOT accept -i to override the image name. Thus I renamed zfcpdump_part.image to zfcpdump-image: root@t35lp25:~# cd /lib/s390-tools/zfcpdump root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 cgroup_disable=memory ' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x001b9fff parmline: 0x001ba000-0x001ba1ff initial ramdisk.: 0x001c-0x0020edff Preparing boot device: sde. Done. root@t35lp25:/lib/s390-tools/zfcpdump# === Hi, zfcpdump_part.image got renamed to zfcpdump-image upstream with s390-tools v2.7.0. For me it looks like the old name is hard coded somewhere in the packaging/installation routines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Can I have the complete list please as I'm trying to figure out if there are missing packages that are the root issue. ** Changed in: zfs-linux (Ubuntu) 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/1849981 Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Incomplete Bug description: Was upgrading to 19.10 and encountered this ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfs-dkms 0.8.1-1ubuntu14 ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 10:28:20 2019 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2013-06-08 (2331 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887218] Re: Ryzen 5 3500U - laptop won't boot when on battery power
Hiya - I get this too. HP 15s-eq0507na: Ryzen 5 3500U + Vega 8 iGPU 8GB DDR4 256GB M.2 NVME SSD Always had this problem since the release of 20.04 - tried w/ secure boot on and off. Haven't tried the iomu=soft thing yet Others evidently have this problem (I swear I saw a thread ab this on launchpad a month ago): https://elementaryos.stackexchange.com/questions/22817/inconsistent-booting-on-battery-ryzen-3500u https://askubuntu.com/questions/1206472/ubuntu-18-04-and-20-04-stuck-on-gnome-startup-on-battery-only Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887218 Title: Ryzen 5 3500U - laptop won't boot when on battery power Status in linux package in Ubuntu: Incomplete Bug description: Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery. For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6. issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942 dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/ iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working. OS: Kubuntu 20.04 LTS CPU: Ryzen 5 3500U GPU: AMD Vega 8 RAM: 8 GB DDR4 2400 Mhz disk: 256 GB nvme I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888695] 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/1888695 Title: (Thinkpad L480) Booting hangs at the spinner screen when an HDMI cable is connected to an external monitor Status in linux package in Ubuntu: Confirmed Bug description: Laptop: Lenovo ThinkPad L480 External monitor: Philips 276E8VJSB (4K UHD) Steps to reproduce the problem: 1. While turned off, connect an HDMI cable between the laptop and an external monitor 2. Turn on the laptop 3. Booting hangs at the spinner screen, where it's written "Press Ctrl+C to skip" The laptop boots up normally when the HDMI cable is not connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 16:08:14 2020 InstallationDate: Installed on 2020-04-26 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2113 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LTS01800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a25a653c-6a2a-4954-bd98-bfe2582a2b74 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.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET60W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 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.modalias: dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS01800 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
$ sudo apt list --installed | grep -i zfs libzfs2linux/focal-updates,focal-updates,now 0.8.3-1ubuntu12.2 amd64 [installed,automatic] zfs-zed/focal-updates,focal-updates,now 0.8.3-1ubuntu12.2 amd64 [installed,automatic] zfsutils-linux/focal-updates,focal-updates,now 0.8.3-1ubuntu12.2 amd64 [installed] -- 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/1849981 Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Confirmed Bug description: Was upgrading to 19.10 and encountered this ProblemType: Package DistroRelease: Ubuntu 19.10 Package: zfs-dkms 0.8.1-1ubuntu14 ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Sat Oct 26 10:28:20 2019 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2013-06-08 (2331 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: zfs-linux Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888695] [NEW] (Thinkpad L480) Booting hangs at the spinner screen when an HDMI cable is connected to an external monitor
Public bug reported: Laptop: Lenovo ThinkPad L480 External monitor: Philips 276E8VJSB (4K UHD) Steps to reproduce the problem: 1. While turned off, connect an HDMI cable between the laptop and an external monitor 2. Turn on the laptop 3. Booting hangs at the spinner screen, where it's written "Press Ctrl+C to skip" The laptop boots up normally when the HDMI cable is not connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 16:08:14 2020 InstallationDate: Installed on 2020-04-26 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2113 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LTS01800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a25a653c-6a2a-4954-bd98-bfe2582a2b74 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.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET60W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 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.modalias: dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS01800 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888695 Title: (Thinkpad L480) Booting hangs at the spinner screen when an HDMI cable is connected to an external monitor Status in linux package in Ubuntu: New Bug description: Laptop: Lenovo ThinkPad L480 External monitor: Philips 276E8VJSB (4K UHD) Steps to reproduce the problem: 1. While turned off, connect an HDMI cable between the laptop and an external monitor 2. Turn on the laptop 3. Booting hangs at the spinner screen, where it's written "Press Ctrl+C to skip" The laptop boots up normally when the HDMI cable is not connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1875 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 16:08:14 2020 InstallationDate: Installed on 2020-04-26 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:2113 Acer, Inc Integrated Camera Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20LTS01800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a25a653c-6a2a-4954-bd98-bfe2582a2b74 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.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET60W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No
[Kernel-packages] [Bug 1886814] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2020-07-23 11:06 EDT---
Hi,
I was able to reproduce the "make: echo: Operation not permitted" on my Ubuntu
20.04 s390x machine.
I've installed build and installed the mentioned make-dfsg_4.3-4ubuntu1 package
without the "--disable-posix-spawn" configure flag.
I've build flatpak-builder_1.0.11-1 which executes the test which is triggering
the "Operation not permitted".
Then I've adjusted the tests, thus I can also run them without building the
package itself.
This test runs flatpak-builder which prepares some stuff (e.g. a root-directory
with all needed files / binaries / libraries).
flatpak-builder then creates a container with bwrap and calls a configure
skript, which generates a Makefile.
In a second invocation, make is invoked.
I've adjusted the configure script which now executed an own small program.
This program is first waiting some time, which I use to deterine its PID. Then
I can either attach strace or gdb.
After the timeout, the program just execve's to make. Thus in the end I have a
process-chain like:
flatpak-builder--bwrap---bwrap---configure---make
The strace output shows, that the clone syscall is failing with EPERM:
4269 17:08:47.914142 stat("/usr/bin/echo", {st_mode=S_IFREG|0755,
st_size=39136, ...}) = 0 <0.03>
4270 17:08:47.914155 geteuid() = 1001 <0.01>
4271 17:08:47.914167 getegid() = 1001 <0.02>
4272 17:08:47.914175 getuid()= 1001 <0.01>
4273 17:08:47.914182 getgid()= 1001 <0.01>
4274 17:08:47.914189 access("/usr/bin/echo", X_OK) = 0 <0.05>
4275 17:08:47.914203 mmap(NULL, 36864, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x3ff9c86b000 <0.02>
4276 17:08:47.914214 rt_sigprocmask(SIG_BLOCK, ~[], [HUP INT QUIT TERM CHLD
XCPU XFSZ], 8) = 0 <0.01>
4277 17:08:47.914224 clone(child_stack=0x3ff9c874000,
flags=CLONE_VM|CLONE_VFORK|SIGCHLD) = -1 EPERM (Operation not permitted)
<0.01>
4278 17:08:47.914235 munmap(0x3ff9c86b000, 36864) = 0 <0.04>
4279 17:08:47.914245 rt_sigprocmask(SIG_SETMASK, [HUP INT QUIT TERM CHLD XCPU
XFSZ], NULL, 8) = 0 <0.01>
A gdb session showed that posix_spawn is called by make like that (Info: make
is using vfork() if configured with "--disable-posix-spawn"):
jobs.c:child_execute_job (struct childbase *child, int good_stdin, char **argv)
posix_spawnattr_t attr;
posix_spawn_file_actions_t fa;
short flags = 0;
posix_spawnattr_init ()
posix_spawn_file_actions_init ()
flags |= POSIX_SPAWN_SETSIGMASK; => 0x08
flags |= POSIX_SPAWN_USEVFORK; => 0x40
fdin=0, fdout=1, fderr=2
flags |= POSIX_SPAWN_RESETIDS; => 0x01
=> flags = 0x49
posix_spawnattr_setflags (, flags)
/* Start the program. */
while ((r = posix_spawn (, cmd, , , argv,
child->environment)) == EINTR)
;
In glibc, the posix_spawn is doing this:
posix_spawn(...) -> __spawni(..., 0) -> __spawnix(..., __execve)
void *stack = __mmap (NULL, stack_size, prot, MAP_PRIVATE | MAP_ANONYMOUS |
MAP_STACK, -1, 0);
/* Disable asynchronous cancellation. */
__libc_signal_block_all ();
# define CLONE(__fn, __stack, __stacksize, __flags, __args) \
__clone (__fn, __stack, __flags, __args)
new_pid = CLONE (__spawni_child, STACK (stack, stack_size), stack_size,
CLONE_VM | CLONE_VFORK | SIGCHLD, );
=> __clone (__spawni_child, __stack, CLONE_VM | CLONE_VFORK | SIGCHLD, );
/sysdeps/unix/sysv/linux/s390/s390-64/clone.S
(gdb) i r r2 r3 r4 r5 r6
r2 0x3ffb22f53c0 4396740989888
r3 0x3ffb24f4000 4396743081984
r4 0x4111 16657
r5 0x3ffce97c9e0 4397217597920
r6 0x 18446744073709551615
? >0x3ffb2306760stg %r6,48(%r15)
? 0x3ffb2306766 lgr %r0,%r5
? 0x3ffb230676a ltgr%r1,%r2
? 0x3ffb230676e je 0x3ffb23067a6
? 0x3ffb2306772 ltgr%r2,%r3
? 0x3ffb2306776 je 0x3ffb23067a6
? 0x3ffb230677a lgr %r3,%r4
? 0x3ffb230677e lgr %r4,%r6
? 0x3ffb2306782 lg %r5,168(%r15)
? 0x3ffb2306788 lg %r6,160(%r15)
(gdb) i r r1 r2 r3 r4 r5 r6
r1 0x3ffb22f53c0 4396740989888
r2 0x3ffb24f4000 4396743081984
r3 0x4111 16657
# define CLONE_VM 0x0100 /* Set if VM shared between processes. */
# define CLONE_VFORK 0x4000 /* Set if the parent wants the child to wake
it up on mm_release. */
/sysdeps/unix/sysv/linux/bits/signum.h:41:#define SIGCHLD 17 => 0x11
r4 0x 18446744073709551615
r5 0x3ffce97c960 4397217597792
r6 0x0 0
/* sys_clone (void *child_stack, unsigned long flags, pid_t *parent_tid, pid_t
*child_tid, void *tls); */
? 0x3ffb230678e svc 120
?
=> sys_clone is
[Kernel-packages] [Bug 1888691] Re: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps
** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1888691 Title: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps Status in snapd: New Status in linux-raspi2 package in Ubuntu: New Bug description: The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does not boot. After it gets to "Starting kernel..." it just stops. Attempting to power off/on the device after the failed boot fails in the uboot script: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 28 ms (161.1 KiB/s) ## Executing script at 0240 4096 bytes read in 39 ms (102.5 KiB/s) 131072 bytes read in 45 ms (2.8 MiB/s) 131072 bytes written in 89 ms (1.4 MiB/s) SCRIPT FAILED: continuing... 45618 bytes read in 41 ms (1.1 MiB/s) Card did not respond to voltage select! starting USB... ... This does not seem to happen with the arm64 kernel, and booting the armhf kernel seems to work fine on pi3 devices - it just seems to be the combination of armhf and rpi4 that breaks right now. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1888691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888691] [NEW] [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps
Public bug reported: The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does not boot. After it gets to "Starting kernel..." it just stops. Attempting to power off/on the device after the failed boot fails in the uboot script: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 28 ms (161.1 KiB/s) ## Executing script at 0240 4096 bytes read in 39 ms (102.5 KiB/s) 131072 bytes read in 45 ms (2.8 MiB/s) 131072 bytes written in 89 ms (1.4 MiB/s) SCRIPT FAILED: continuing... 45618 bytes read in 41 ms (1.1 MiB/s) Card did not respond to voltage select! starting USB... ... This does not seem to happen with the arm64 kernel, and booting the armhf kernel seems to work fine on pi3 devices - it just seems to be the combination of armhf and rpi4 that breaks right now. ** Affects: snapd Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: uc20 ** Tags added: uc20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1888691 Title: [uc20] rpi4 does not boot with armhf on recent 5.4 kernel snaps Status in snapd: New Status in linux-raspi2 package in Ubuntu: New Bug description: The armhf kernel on the current uc20 beta image (5.4.0-1011.11 r156) boots fine on rpi4, but when the system refreshes to 5.4.0-1011.15 r179, the system does not boot. After it gets to "Starting kernel..." it just stops. Attempting to power off/on the device after the failed boot fails in the uboot script: Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 28 ms (161.1 KiB/s) ## Executing script at 0240 4096 bytes read in 39 ms (102.5 KiB/s) 131072 bytes read in 45 ms (2.8 MiB/s) 131072 bytes written in 89 ms (1.4 MiB/s) SCRIPT FAILED: continuing... 45618 bytes read in 41 ms (1.1 MiB/s) Card did not respond to voltage select! starting USB... ... This does not seem to happen with the arm64 kernel, and booting the armhf kernel seems to work fine on pi3 devices - it just seems to be the combination of armhf and rpi4 that breaks right now. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1888691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Hi all, Currently grub is frozen in all series for point releases. So I will start the SRU after focal point release, please just use #105 with a "sudo update-grub" as a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Triaged Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Kernel-packages] [Bug 1888690] [NEW] Xenial update: v4.4.231 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v4.4.231 upstream stable release
from git://git.kernel.org/
KVM: s390: reduce number of IO pins to 1
spi: spidev: fix a race between spidev_release and spidev_remove
spi: spidev: fix a potential use-after-free in spidev_release()
scsi: mptscsih: Fix read sense data size
net: cxgb4: fix return error value in t4_prep_fw
smsc95xx: check return value of smsc95xx_reset
smsc95xx: avoid memory leak in smsc95xx_bind
ALSA: compress: fix partial_drain completion state
arm64: kgdb: Fix single-step exception handling oops
ALSA: opl3: fix infoleak in opl3
ALSA: hda - let hs_mic be picked ahead of hp_mic
ALSA: usb-audio: add quirk for MacroSilicon MS2109
KVM: x86: bit 8 of non-leaf PDPEs is not reserved
Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"
btrfs: fix fatal extent_buffer readahead vs releasepage race
drm/radeon: fix double free
ARC: entry: fix potential EFA clobber when TIF_SYSCALL_TRACE
ARC: elf: use right ELF_ARCH
bnxt_en: fix NULL dereference in case SR-IOV configuration fails
ipv4: fill fl4_icmp_{type,code} in ping_v4_sendmsg
l2tp: remove skb_dst_set() from l2tp_xmit_skb()
llc: make sure applications use ARPHRD_ETHER
net: Added pointer check for dst->ops->neigh_lookup in dst_neigh_lookup_skb
genetlink: remove genl_bind
tcp: make sure listeners don't initialize congestion-control state
tcp: md5: add missing memory barriers in tcp_md5_do_add()/tcp_md5_hash_key()
tcp: md5: refine tcp_md5_do_add()/tcp_md5_hash_key() barriers
tcp: md5: allow changing MD5 keys in all socket states
i2c: eg20t: Load module automatically if ID matches
Revert "usb/ehci-platform: Set PM runtime as active on resume"
Revert "usb/xhci-plat: Set PM runtime as active on resume"
Revert "usb/ohci-platform: Fix a warning when hibernating"
usb: gadget: udc: atmel: fix uninitialized read in debug printk
staging: comedi: verify array index is correct before using it
perf stat: Zero all the 'ena' and 'run' array slot stats for interval mode
mtd: rawnand: brcmnand: fix CS0 layout
HID: magicmouse: do not set up autorepeat
usb: core: Add a helper function to check the validity of EP type in URB
ALSA: line6: Perform sanity check for each URB creation
ALSA: usb-audio: Fix race against the error recovery URB submission
USB: c67x00: fix use after free in c67x00_giveback_urb
usb: chipidea: core: add wakeup support for extcon
usb: gadget: function: fix missing spinlock in f_uac1_legacy
USB: serial: iuu_phoenix: fix memory corruption
USB: serial: cypress_m8: enable Simply Automated UPB PIM
USB: serial: ch341: add new Product ID for CH340
USB: serial: option: add GosunCn GM500 series
USB: serial: option: add Quectel EG95 LTE modem
virtio: virtio_console: add missing MODULE_DEVICE_TABLE() for rproc serial
fuse: Fix parameter for FS_IOC_{GET,SET}FLAGS
mei: bus: don't clean driver pointer
Input: i8042 - add Lenovo XiaoXin Air 12 to i8042 nomux list
uio_pdrv_genirq: fix use without device tree and no interrupt
MIPS: Fix build for LTS kernel caused by backporting lpj adjustment
hwmon: (emc2103) fix unable to change fan pwm1_enable attribute
dmaengine: fsl-edma: Fix NULL pointer exception in fsl_edma_tx_handler
misc: atmel-ssc: lock with mutex instead of spinlock
sched/fair: handle case of task_h_load() returning 0
Linux 4.4.231
UBUNTU: upstream stable to v4.4.231
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-
[Kernel-packages] [Bug 1888570] 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 1888570 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: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Incomplete Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876715] Comment bridged from LTC Bugzilla
--- Comment From pr...@de.ibm.com 2020-07-23 10:08 EDT--- (In reply to comment #10) > Hi, were the s390-tools maintainer able to dive deeper into this? Hi, I'm no s390-tools maintainer but I guess in the long run it's easiest when you rebuild the zfcpdump kernel with the new names otherwise ubuntu will be decoupled from upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk: root@t35lp25:/~# apt install zfcpdump-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: zfcpdump-kernel 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 1655 kB of archives. After this operation, 1757 kB of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB] Fetched 1655 kB in 1s (1803 kB/s) Selecting previously unselected package zfcpdump-kernel. (Reading database ... 53866 files and directories currently installed.) Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ... Unpacking zfcpdump-kernel (4.13-0ubuntu1) ... Setting up zfcpdump-kernel (4.13-0ubuntu1) ... root@t35lp25:/~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for partition dump: No such file or directory root@t35lp25:~# ls /lib/s390-tools/zfcpdump/ zfcpdump-initrd zfcpdump_part.image root@t35lp25:~# As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is available. with paramater -d, zipl does NOT accept -i to override the image name. Thus I renamed zfcpdump_part.image to zfcpdump-image: root@t35lp25:~# cd /lib/s390-tools/zfcpdump root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 cgroup_disable=memory ' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x001b9fff parmline: 0x001ba000-0x001ba1ff initial ramdisk.: 0x001c-0x0020edff Preparing boot device: sde. Done. root@t35lp25:/lib/s390-tools/zfcpdump# === Hi, zfcpdump_part.image got renamed to zfcpdump-image upstream with s390-tools v2.7.0. For me it looks like the old name is hard coded somewhere in the packaging/installation routines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865965] Re: kill11 from ubuntu_ltp_syscalls failed
** Changed in: ubuntu-kernel-tests Status: New => Confirmed ** Tags added: hwe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865965 Title: kill11 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: startup='Tue Mar 3 15:46:25 2020' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s kill11.c:97: PASS: signal SIGHUP kill11.c:97: PASS: signal SIGINT kill11.c:97: PASS: signal SIGQUIT dumped core kill11.c:97: PASS: signal SIGILL dumped core kill11.c:97: PASS: signal SIGTRAP dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGIOT/SIGABRT dumped core kill11.c:97: PASS: signal SIGBUS dumped core kill11.c:97: PASS: signal SIGFPE dumped core kill11.c:97: PASS: signal SIGKILL kill11.c:97: PASS: signal SIGUSR1 kill11.c:97: PASS: signal SIGSEGV dumped core kill11.c:97: PASS: signal SIGUSR2 kill11.c:97: PASS: signal SIGPIPE kill11.c:97: PASS: signal SIGALRM kill11.c:97: PASS: signal SIGTERM kill11.c:97: PASS: signal SIGSTKFLT kill11.c:97: PASS: signal SIGXCPU dumped core Test timeouted, sending SIGKILL! tst_test.c:1269: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1270: BROK: Test killed! (timeout?) Summary: passed 18 failed 0 skipped 0 warnings 0 tag=kill11 stime=1583250385 dur=302 exit=exited stat=2 core=no cu=0 cs=0 Need to see if bump the timeout threshold can help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1865965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
** 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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: New Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** This bug is no longer a duplicate of bug 1573095 Cloud images fail to boot when a serial port is not available ** No longer affects: linux (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => In Progress ** Also affects: initramfs-tools (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Groovy) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Changed in: initramfs-tools (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: initramfs-tools (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: initramfs-tools (Ubuntu Xenial) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Trusty) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Xenial) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Trusty) Importance: High => Low ** Changed in: initramfs-tools (Ubuntu Bionic) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Focal) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: initramfs-tools (Ubuntu Eoan) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: initramfs-tools (Ubuntu Xenial) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: initramfs-tools (Ubuntu Trusty) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: In Progress Status in initramfs-tools source package in Bionic: In Progress Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Groovy: In Progress Bug description: kernel get stucks at boot if console=ttyS* is specified in the kernel cmdline and that serial HW isn't available on the system. Reproduced with: 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline) Removing the non-existent 'console=ttyS*' parameter fixes the situation. I tested it using KVM/qemu, but it has been brought to my attention that it was reproducible in VMware as well. I think it is safe to say that it is unlikely to be specifics to a certain virtualization technology type. Didn't test on baremetal yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] [NEW] poweroff not working after apt upgrade
You have been subscribed to a public bug: System-Information: Description:Ubuntu 18.04.4 LTS Release:18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- poweroff not working after apt upgrade https://bugs.launchpad.net/bugs/1888570 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 1888523] Re: PCIe Bus Error device 8086:a298 spam
Hi Pedro, It's curious that the message is repeatedly showing up at the rate of a few seconds. It would initially suggest something might be wrong with the PCI device. (As Alex mentioned the errors are correctable, so not a serious issue, but the fact they're being repeatedly logged doesn't sound too right.) Could you please upload the output of these commands (PCI and kernel version information): $ lspci -nnvv > lspci_-nnvv 2>&1 $ lspci -tv > lspci_-tv 2>&1 $ uname -rv > uname_-rv 2>&1 cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[
[Kernel-packages] [Bug 1888647] Re: Realtek wifi dont work after update
*It -> https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1888647 works! -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Incomplete Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel
[Kernel-packages] [Bug 1888647] Re: Realtek wifi dont work after update
It works! -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Incomplete Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4 01:00.0 Ethernet controller: Realtek
[Kernel-packages] [Bug 1888510] Re: xen-netfront: potential deadlock in xennet_remove()
** Also affects: linux-aws-5.3 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-aws (Ubuntu Eoan) ** No longer affects: linux-aws-5.3 (Ubuntu Eoan) ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws-5.3 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-aws-5.3 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-aws-5.3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1888510 Title: xen-netfront: potential deadlock in xennet_remove() Status in linux-aws package in Ubuntu: New Status in linux-aws-5.3 package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Status in linux-aws-5.3 source package in Bionic: New Status in linux-aws source package in Focal: New Status in linux-aws-5.3 source package in Focal: Invalid Bug description: [Impact] During our AWS testing we were experiencing deadlocks on hibernate across all Xen instance types. The trace was showing that the system was stuck in xennet_remove(): [ 358.109087] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 358.115102] modprobeD0 4892 4833 0x4004 [ 358.115104] Call Trace: [ 358.115112] __schedule+0x2a8/0x670 [ 358.115115] schedule+0x33/0xa0 [ 358.115118] xennet_remove+0x1f0/0x230 [xen_netfront] [ 358.115121] ? wait_woken+0x80/0x80 [ 358.115124] xenbus_dev_remove+0x51/0xa0 [ 358.115126] device_release_driver_internal+0xe0/0x1b0 [ 358.115127] driver_detach+0x49/0x90 [ 358.115129] bus_remove_driver+0x59/0xd0 [ 358.115131] driver_unregister+0x2c/0x40 [ 358.115132] xenbus_unregister_driver+0x12/0x20 [ 358.115134] netif_exit+0x10/0x7aa [xen_netfront] [ 358.115137] __x64_sys_delete_module+0x146/0x290 [ 358.115140] do_syscall_64+0x5a/0x130 [ 358.115142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This prevented hibernation to complete. The reason of this problem is a race condition in xennet_remove(): the system is reading the current state of the bus, it's requesting to change the state to "Closing", and it's waiting for the state to be changed to "Closing". However, if the state becomes "Closed" between reading the state and requesting the state change, we are stuck forever, because the state will never change from "Closed" back to "Closing". [Test case] Create any Xen-based instance in AWS, hibernate/resume multiple times. Some times the system gets stuck (hung task timeout). [Fix] Prevent the deadlock by changing the wait condition to check also for state == Closed. [Regression potential] Minimal, this change affects only Xen, more exactly only the xen- netfront driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888647] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1888647/+attachment/5395206/+files/ProcEnviron.txt -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Incomplete Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel
[Kernel-packages] [Bug 1888647] Re: Realtek wifi dont work after update
apport information ** Tags added: apport-collected bionic ** Description changed: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 02a4 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c822 03:00.0 Unassigned class [ff00]: Realtek
[Kernel-packages] [Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects
Hi, were the s390-tools maintainer able to dive deeper into this? ** Changed in: ubuntu-z-systems Status: Triaged => 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/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk: root@t35lp25:/~# apt install zfcpdump-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: zfcpdump-kernel 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 1655 kB of archives. After this operation, 1757 kB of additional disk space will be used. Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB] Fetched 1655 kB in 1s (1803 kB/s) Selecting previously unselected package zfcpdump-kernel. (Reading database ... 53866 files and directories currently installed.) Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ... Unpacking zfcpdump-kernel (4.13-0ubuntu1) ... Setting up zfcpdump-kernel (4.13-0ubuntu1) ... root@t35lp25:/~# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for partition dump: No such file or directory root@t35lp25:~# ls /lib/s390-tools/zfcpdump/ zfcpdump-initrd zfcpdump_part.image root@t35lp25:~# As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is available. with paramater -d, zipl does NOT accept -i to override the image name. Thus I renamed zfcpdump_part.image to zfcpdump-image: root@t35lp25:~# cd /lib/s390-tools/zfcpdump root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d /dev/disk/by-id/scsi-36005076303ffd3274609-part1 Building bootmap directly on partition '/dev/disk/by-id/scsi-36005076303ffd3274609-part1' Adding dump section initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 cgroup_disable=memory ' component address: heap area...: 0x2000-0x5fff stack area..: 0xf000-0x internal loader.: 0xa000-0xdfff parameters..: 0x9000-0x91ff kernel image: 0x0001-0x001b9fff parmline: 0x001ba000-0x001ba1ff initial ramdisk.: 0x001c-0x0020edff Preparing boot device: sde. Done. root@t35lp25:/lib/s390-tools/zfcpdump# === Hi, zfcpdump_part.image got renamed to zfcpdump-image upstream with s390-tools v2.7.0. For me it looks like the old name is hard coded somewhere in the packaging/installation routines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
