[Kernel-packages] [Bug 1818319] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242774/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242767/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242772/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242777/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242776/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242770/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242771/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242778/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242775/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242773/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242769/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242768/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7LCN22WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IKB dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: dmi.product.family: YOGA 730-13IKB dmi.product.name: 81CT dmi.product.version: Lenovo YOGA 730-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] Re: r8822be module not signed
apport information ** Tags added: apport-collected bionic staging ** Description changed: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: michel 1915 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-01-08 (52 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. + Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. + Bus 001 Device 002: ID 13d3:56b2 IMC Networks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 81CT + 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 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-45-generic N/A + linux-backports-modules-4.15.0-45-generic N/A + linux-firmware 1.173.3 + StagingDrivers: r8822be + Tags: bionic staging + Uname: Linux 4.15.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 03/14/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: 7LCN22WW(V1.03) + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40709 WIN + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 31 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo YOGA 730-13IKB + dmi.modalias: dmi:bvnLENOVO:bvr7LCN22WW(V1.03):bd03/14/2018:svnLENOVO:pn81CT:pvrLenovoYOGA730-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IKB: + dmi.product.family: YOGA 730-13IKB + dmi.product.name: 81CT + dmi.product.version: Lenovo YOGA 730-13IKB + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1818319/+attachment/5242766/+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/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michel 1915 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-08 (52 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b023 Realtek Semiconductor Corp. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 13d3:56b2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81CT 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=ea00ea24-80ae-4482-b1d8-b43d79251943 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 StagingDrivers: r8822be Tags: bionic staging Uname:
[Kernel-packages] [Bug 1818319] 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 1818319 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: Incomplete Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818319] [NEW] r8822be module not signed
Public bug reported: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: r8822be secure-boot wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818319 Title: r8822be module not signed Status in linux package in Ubuntu: New Bug description: I have a Lenovo Yoga 730-13 running Ubuntu 18.04. UEFI. When booting in secure boot mode the wifi module realtek r8822be is not recognized because it appears the r8822be kernel module is not signed : Demsg : 2.526831] r8822be: module is from the staging directory, the quality is unknown, you have been warned. [2.527087] r8822be: module verification failed: signature and/or required key missing - tainting kernel Please advise on a possible fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818319/+subscriptions -- Mailing list: https://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 1550779] Re: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
-- Forwarded message - From: 678 <678sh...@gmail.com> Date: Sat, Mar 2, 2019 at 10:11 AM Subject: Re: [Bug 1550779] Re: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches To: Bug 1550779 <1550...@bugs.launchpad.net> On 02/03/19 12:40 AM, Tom Mittelstaedt wrote: > complement (sorry for multiple-comments): > > > $ dmesg | grep i915 > [1.439662] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem > [1.439938] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27) > [1.443269] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on minor 0 > [1.523397] i915 :00:02.0: fb0: inteldrmfb frame buffer device > [ 15.764955] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) > [56162.413053] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [59291.355801] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [64022.043888] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [68572.684020] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [84907.749926] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [131695.137832] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [140974.062510] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [152485.446459] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [155522.518586] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [164965.550908] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [165879.406055] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [178549.854547] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [185381.350517] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [187311.834886] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [188858.938318] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [195515.961747] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [195618.444271] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [206235.029303] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [217208.530378] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [222859.639505] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [225820.223051] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [231471.431276] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [239098.879129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [242398.343295] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [247190.079036] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [247912.015060] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [248846.631100] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > [258283.737675] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > > > Of course everything is up to date. > Yes thank for the observation 678sh...@gmail.com But may I add and hope you are talking about my system , I am using a Dell lap top purchased during 2006 with (bio date not remembered yet ,and later the bio date status changed without my knowledge, some time back). I am not a tech/ expert ,but experiment with all type linux and different flavors of ubuntu .What I know is bios not reboot automatically ,every time i open system, i have to reset bio. The system has very severe remote interference and do not have a stable status. Becasue of my driving experience (ignorant certainly), I manage some how this desktop and run things.:-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue repro
Re: [Kernel-packages] [Bug 1550779] Re: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Certainly there is bug position which is continuing with my machine and programe need attention.. On Sat, Mar 2, 2019 at 11:55 AM Shaju കോട്ടയം <678sh...@gmail.com> wrote: > > > -- Forwarded message - > From: 678 <678sh...@gmail.com> > Date: Sat, Mar 2, 2019 at 10:11 AM > Subject: Re: [Bug 1550779] Re: [Lenovo ThinkPad X220] *ERROR* CPU pipe A > FIFO underrun - Xorg glitches > To: Bug 1550779 <1550...@bugs.launchpad.net> > > > > On 02/03/19 12:40 AM, Tom Mittelstaedt wrote: > > complement (sorry for multiple-comments): > > > > > > $ dmesg | grep i915 > > [1.439662] i915 :00:02.0: vgaarb: changed VGA decodes: > olddecodes=io+mem,decodes=io+mem:owns=io+mem > > [1.439938] [drm] Finished loading DMC firmware > i915/skl_dmc_ver1_27.bin (v1.27) > > [1.443269] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on > minor 0 > > [1.523397] i915 :00:02.0: fb0: inteldrmfb frame buffer device > > [ 15.764955] snd_hda_intel :00:1f.3: bound :00:02.0 (ops > i915_audio_component_bind_ops [i915]) > > [56162.413053] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [59291.355801] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [64022.043888] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [68572.684020] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [84907.749926] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [131695.137832] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [140974.062510] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [152485.446459] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [155522.518586] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [164965.550908] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [165879.406055] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [178549.854547] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [185381.350517] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [187311.834886] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [188858.938318] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [195515.961747] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [195618.444271] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [206235.029303] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [217208.530378] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [222859.639505] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [225820.223051] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [231471.431276] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [239098.879129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [242398.343295] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [247190.079036] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [247912.015060] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [248846.631100] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > [258283.737675] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe A FIFO underrun > > > > > > Of course everything is up to date. > > > Yes thank for the observation > > 678sh...@gmail.com > > But may I add and hope you are talking about my system , I am using a > Dell lap top purchased during 2006 with (bio date not remembered yet > ,and later the bio date status changed without my knowledge, some time > back). I am not a tech/ expert ,but experiment with all type linux and > different flavors of ubuntu .What I know is bios not reboot > automatically ,every time i open system, i have to reset bio. The system > has very severe remote interference and do not have a stable status. > > Becasue of my driving experience (ignorant certainly), I manage some > how this desktop and run things.:-) > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description:
[Kernel-packages] [Bug 1765998] Re: FS access deadlock with btrfs quotas enabled
Hm, it's been a while... I think back then I made some btrfs developers aware of it on IRC, but never got around to sending it to the mailing list. I'm running my own kernel builds for now (I had to do that to fix some other issues anyway) with the patch from comment #4 applied, which seems to reliably fix this issue. I am very occasionally getting parent transid verify errors on the quota tree though, which I believe must be originating from another bug added at some point after I posted that patch here, because initially I didn't have any of those for several months. It seems that those can be cleaned up by temporarily disabling and re-enabling quota, so they are no big deal to me right now, despite causing some annoying downtime occasionally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765998 Title: FS access deadlock with btrfs quotas enabled Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: I'm running into an issue on Ubuntu Bionic (but not Xenial) where shortly after boot, under heavy load from many LXD containers starting at once, access to the btrfs filesystem that the containers are on deadlocks. The issue is quite hard to reproduce on other systems, quite likely related to the size of the filesystem involved (4 devices with a total of 8TB, millions of files, ~20 subvolumes with tens of snapshots each) and the access pattern from many LXD containers at once. It definitely goes away when disabling btrfs quotas though. Another prerequisite to trigger this bug may be the container subvolumes sharing extents (from their parent image or due to deduplication). I can only reliably reproduce it on a production system that I can only do very limited testing on, however I have been able to gather the following information: - Many threads are stuck, trying to aquire locks on various tree roots, which are never released by their current holders. - There always seem to be (at least) two threads executing rmdir syscalls which are creating the circular dependency: One of them is in btrfs_cow_block => ... => btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants to acquire a lock that was already aquired by btrfs_search_slot of the other rmdir. - Reverting this patch seems to prevent it from happening: https://patchwork.kernel.org/patch/9573267/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 (linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge) derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1814749 Title: linux: 4.18.0-16.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 (linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge) derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 (linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge) derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1814749 Title: linux: 4.18.0-16.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 (linux-aws-edge), bug 1814754 (linux-gcp-edge), bug 1814761 (linux-azure-edge) derivatives: bug 1816782 (linux-azure), bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818312] 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/1818312 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: ao atualizar ubuntu 14.04 para 16.04 falhou ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-142-generic 4.4.0-142.168 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 1 20:19:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=8538fa6e-bee5-47aa-97fa-7a7b15339443 InstallationDate: Installed on 2019-02-27 (2 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5452 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic.efi.signed root=UUID=6bd9655f-18b6-4af1-9526-d4957fb84cd0 ro quiet splash radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux StagingDrivers: rts5139 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2019-03-01 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0F77J1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.1 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd04/25/2016:svnDellInc.:pnInspiron5452:pvr1.4.1:rvnDellInc.:rn0F77J1:rvrA00:cvnDellInc.:ct8:cvr1.4.1: dmi.product.name: Inspiron 5452 dmi.product.version: 1.4.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818312] Re: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818312 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: ao atualizar ubuntu 14.04 para 16.04 falhou ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-142-generic 4.4.0-142.168 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 1 20:19:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=8538fa6e-bee5-47aa-97fa-7a7b15339443 InstallationDate: Installed on 2019-02-27 (2 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5452 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic.efi.signed root=UUID=6bd9655f-18b6-4af1-9526-d4957fb84cd0 ro quiet splash radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux StagingDrivers: rts5139 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2019-03-01 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0F77J1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.1 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd04/25/2016:svnDellInc.:pnInspiron5452:pvr1.4.1:rvnDellInc.:rn0F77J1:rvrA00:cvnDellInc.:ct8:cvr1.4.1: dmi.product.name: Inspiron 5452 dmi.product.version: 1.4.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818312] [NEW] package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: ao atualizar ubuntu 14.04 para 16.04 falhou ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-142-generic 4.4.0-142.168 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 1 20:19:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=8538fa6e-bee5-47aa-97fa-7a7b15339443 InstallationDate: Installed on 2019-02-27 (2 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5452 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic.efi.signed root=UUID=6bd9655f-18b6-4af1-9526-d4957fb84cd0 ro quiet splash radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux StagingDrivers: rts5139 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2019-03-01 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0F77J1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.1 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd04/25/2016:svnDellInc.:pnInspiron5452:pvr1.4.1:rvnDellInc.:rn0F77J1:rvrA00:cvnDellInc.:ct8:cvr1.4.1: dmi.product.name: Inspiron 5452 dmi.product.version: 1.4.1 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package staging xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818312 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in linux package in Ubuntu: Confirmed Bug description: ao atualizar ubuntu 14.04 para 16.04 falhou ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-142-generic 4.4.0-142.168 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 1 20:19:09 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=8538fa6e-bee5-47aa-97fa-7a7b15339443 InstallationDate: Installed on 2019-02-27 (2 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 5452 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic.efi.signed root=UUID=6bd9655f-18b6-4af1-9526-d4957fb84cd0 ro quiet splash radeon.modeset=0 nouveau.modeset=0 i915.disable_power_well=0 video.use_native_backlight=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux StagingDrivers: rts5139 Title: package linux-image-4.4.0-142-generic 4.4.0-142.168 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2019-03-01 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0F77J1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.1 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd04/25/2016:svnDellInc.:pnInspiron5452:pvr1.4.1:rvnDellInc.:rn0F77J1:rvrA00:cvnDellInc.:ct8:cvr1.4.1: dmi.product.name: Inspiron 5452 dmi.product.version: 1.4.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818312/+subscripti
[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
Related public bug report: https://bugs.launchpad.net/nvidia/+bug/1818101 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814647 Title: linux: 4.4.0-143.169 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817740] Re: Disable ZFS
** Changed in: linux-azure (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1817740 Title: Disable ZFS Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Trusty: Fix Committed Bug description: [Impact] ZFS was not supposed to be enabled on linux-azure for trusty from the start. There is no ZFS tooling in trusty anyway. [Regression potential] Some user will complain they cannot mount their ZFS now with that kernel. They can just install a different kernel then, as this one was not supposed to be used like that. [Test case] zfs is disabled on the files after copy-files is run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1817740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] 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 1818294 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
I will, as soon as possible - but the 5.0rc1 mainline build has totally failed to boot, and I'm stuck waiting on remote hands before I can get more investigation done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: New Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
Thanks for subscribing me. I'd like to get to the bottom of your specific issue and get that addressed vs. dumping a bunch more patches in and hoping it fixes it. To aide in that, can you provide additional information about the issue? There should be an auto-update to this bug soon that provides a list of data to collect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: New Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
Meanwhile, can you confirm whether or not this impacts the 4.18-based HWE kernel in 18.04? See: https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: New Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818294] [NEW] HiSilicon HNS ethernet broken in 4.15.0-45
Public bug reported: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: New Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810588] Re: Touchpad not detected by kernel
It worked fine! Do you know when is that going to final release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810588 Title: Touchpad not detected by kernel Status in linux package in Ubuntu: Confirmed Bug description: The touchpad installed on my notebook is not detected by the kernel. I searched for the solution, but it's not even detected. I also attached more debug info to the bug report. My problem is similar to this one: https://askubuntu.com/questions/943320/touchpad-not-detected-in-any- linux-distribution I followed this link to make the report: https://wiki.ubuntu.com/DebuggingTouchpadDetection xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ HD Webcam: HD Webcamid=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonna 2785 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 5 10:12:23 2019 InstallationDate: Installed on 2019-01-04 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Avell High Performance 1513 series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=e98db4ab-9efe-4be0-916a-1b0110afade3 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2019-01-05 (0 days ago) dmi.bios.date: 11/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.10 dmi.board.asset.tag: Standard dmi.board.name: GI5CN5E dmi.board.vendor: Avell High Performance dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.10:bd11/09/2018:svnAvellHighPerformance:pn1513series:pvrStandard:rvnAvellHighPerformance:rnGI5CN5E:rvrStandard:cvnAvellHighPerformance:ct10:cvrStandard: dmi.product.family: Titanium dmi.product.name: 1513 series dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: Avell High Performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810588/+subscriptions -- Mailing list: https://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 1810457] Re: Update hisilicon SoC-specific drivers
On Fri, Mar 1, 2019 at 12:15 PM directhex wrote: > > Guess what! These changes... regressed my hardware. Thanks for the report. Please provide a new bug report in which to track these issues, and note the LP # here. Also, please confirm that you are using the latest firmware for your device. -dann -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] The Ubuntu server certification suite, which includes network and storage tests. [Fix] Backport the localized driver changes up to v5.0-rc1. [Regression Risk] These changes are restricted to the hns and hisi_sas drivers, which only impact the D05 and D06 server development board platforms. To mitigate this risk, we have explicitly tested the proposed changes on these 2 platforms - changes are staged in ppa:pearl2-team/test. Of course, there is risk that these changes introduced regressions that our testing did not catch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799443] Re: Firmware missing for Raspberry Pi 3
WiFi files are now included but have different names https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=638a91ab5d066929d92c808e064c295a3ccab41d -- 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/1799443 Title: Firmware missing for Raspberry Pi 3 Status in linux-firmware package in Ubuntu: New Bug description: The Raspberry Pi 3 WiFi does not work out of the box due to missing file brcmfmac43430-sdio.txt. The pi's Bluetooth also doesn't work, also due to missing firmware files. Some discussion about licenses for these files is here https://github.com/RPi-Distro/firmware-nonfree/issues/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1799443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
Thanks to Alberto I can confirm the nvidia-384 (nvidia-graphics- drivers-384 - 384.130-0ubuntu0.16.04.2~ppa1 ) from the nvidia-driver- staging ppa works on the customer image. But we still have other dkms modules that still cannot be built properly. The new kernel can't be then installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814647 Title: linux: 4.4.0-143.169 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
I am seeing this occur on 16.04 and that too only on my home network. I am using a D-Link DIR-150M router. Hope this helps in solving this bug. $ dmesg | grep 'ath10k\|wlp5s0' [43748.066244] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready [43798.366800] wlp5s0: AP 18:0f:76:8d:56:b4 changed bandwidth, new config is 2412 MHz, width 2 (2422/0 MHz) [43798.405413] ath10k_pci :05:00.0: firmware crashed! (guid 73bf7f34-1cb6-4cdc-90a8-15e5913458a6) [43798.405466] ath10k_pci :05:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901 [43798.405480] ath10k_pci :05:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [43798.407173] ath10k_pci :05:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7 [43798.408288] ath10k_pci :05:00.0: board_file api 2 bmi_id N/A crc32 93da0176 [43798.408308] ath10k_pci :05:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [43798.410347] ath10k_pci :05:00.0: firmware register dump: [43798.410371] ath10k_pci :05:00.0: [00]: 0x05020001 0x15B3 0x00985B3A 0x00955B31 [43798.410385] ath10k_pci :05:00.0: [04]: 0x00985B3A 0x00060730 0x0004 0x [43798.410402] ath10k_pci :05:00.0: [08]: 0x00955A00 0x00438830 0x00450888 0x00420970 [43798.410416] ath10k_pci :05:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [43798.410430] ath10k_pci :05:00.0: [16]: 0x00952CC4 0x0091080D 0x 0x [43798.410445] ath10k_pci :05:00.0: [20]: 0x40985B3A 0x0040E788 0x0040 0x00421888 [43798.410458] ath10k_pci :05:00.0: [24]: 0x809BF546 0x0040E7E8 0x00426470 0xC0985B3A [43798.410473] ath10k_pci :05:00.0: [28]: 0x809B90D8 0x0040E958 0x0018 0x0042EA0C [43798.410486] ath10k_pci :05:00.0: [32]: 0x809B859A 0x0040E9A8 0x0040E9CC 0x00428D74 [43798.410501] ath10k_pci :05:00.0: [36]: 0x8091D252 0x0040E9C8 0x 0x0001 [43798.410514] ath10k_pci :05:00.0: [40]: 0x809EDD7B 0x0040EA78 0x00437544 0x00429428 [43798.410527] ath10k_pci :05:00.0: [44]: 0x809EB6A6 0x0040EA98 0x00437544 0x0001 [43798.410541] ath10k_pci :05:00.0: [48]: 0x80911210 0x0040EAE8 0x0010 0x004041D0 [43798.410555] ath10k_pci :05:00.0: [52]: 0x80911154 0x0040EB28 0x0040 0x [43798.410569] ath10k_pci :05:00.0: [56]: 0x8091122D 0x0040EB48 0x 0x00400600 [43798.410580] ath10k_pci :05:00.0: Copy Engine register dump: [43798.410609] ath10k_pci :05:00.0: [00]: 0x00034400 5 5 3 3 [43798.410637] ath10k_pci :05:00.0: [01]: 0x00034800 26 26 327 328 [43798.410666] ath10k_pci :05:00.0: [02]: 0x00034c00 16 16 15 16 [43798.410694] ath10k_pci :05:00.0: [03]: 0x00035000 29 29 30 29 [43798.410723] ath10k_pci :05:00.0: [04]: 0x00035400 2767 2767 169 105 [43798.410750] ath10k_pci :05:00.0: [05]: 0x00035800 0 0 0 0 [43798.410777] ath10k_pci :05:00.0: [06]: 0x00035c00 25 25 25 25 [43798.410805] ath10k_pci :05:00.0: [07]: 0x00036000 1 1 1 1 [43798.521863] ieee80211 phy0: Hardware restart was requested [43799.226364] ath10k_pci :05:00.0: device successfully recovered [43929.850037] wlp5s0: AP 18:0f:76:8d:56:b4 changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz) [43967.592805] wlp5s0: deauthenticating from 18:0f:76:8d:56:b4 by local choice (Reason: 3=DEAUTH_LEAVING) -- 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/1730331 Title: ath10k_pci: firmware crashed! Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware package in Fedora: Unknown Bug description: ... Nov 4 18:35:50 akane kernel: [ 10.216896] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 10.216908] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 10.217641] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 10.228600] kvm: Nested Virtualization enabled Nov 4 18:35:50 akane kernel: [ 10.228611] kvm: Nested Paging enabled Nov 4 18:35:50 akane kernel: [ 10.258913] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 10.263535] MCE: In-kernel MCE decoding enabled. Nov 4 18:35:50 akane kernel: [ 10.271401] EDAC amd64: Node 0: DRAM ECC enabled. Nov 4 18:35:50 akane kernel: [ 10.271416] EDAC amd64: F16h_M30h detected (node 0). Nov 4 18:35:50 akane kernel: [ 10.271491] EDAC MC: DCT0 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271494] EDAC amd64: MC: 0: 4096MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271523] EDAC amd64: MC: 2: 0MB 3:
[Kernel-packages] [Bug 1810457] Re: Update hisilicon SoC-specific drivers
Mainline 5.0rc8 kernel is fine, so it's either something that was broken in mainline between rc1 (when this patch was applied in ubuntu) and rc8, or a general bug in the backporting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] The Ubuntu server certification suite, which includes network and storage tests. [Fix] Backport the localized driver changes up to v5.0-rc1. [Regression Risk] These changes are restricted to the hns and hisi_sas drivers, which only impact the D05 and D06 server development board platforms. To mitigate this risk, we have explicitly tested the proposed changes on these 2 platforms - changes are staged in ppa:pearl2-team/test. Of course, there is risk that these changes introduced regressions that our testing did not catch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
Same issue here with a Dell inspiron 7373, I can see the trash messages in the virtual terminals after recover from suspend making them useless. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550779] Re: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
complement (sorry for multiple-comments): $ dmesg | grep i915 [1.439662] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.439938] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27) [1.443269] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on minor 0 [1.523397] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 15.764955] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [56162.413053] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [59291.355801] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [64022.043888] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [68572.684020] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [84907.749926] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [131695.137832] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [140974.062510] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [152485.446459] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [155522.518586] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [164965.550908] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [165879.406055] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [178549.854547] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [185381.350517] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [187311.834886] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [188858.938318] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [195515.961747] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [195618.444271] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [206235.029303] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [217208.530378] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [222859.639505] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [225820.223051] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [231471.431276] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [239098.879129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [242398.343295] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [247190.079036] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [247912.015060] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [248846.631100] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [258283.737675] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Of course everything is up to date. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd6
[Kernel-packages] [Bug 1550779] Re: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches
Let me join this with the following `dmesg | tail`: [Feb24 23:34] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 00:23] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 01:57] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 04:04] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 04:59] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 06:19] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 06:31] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [Feb25 06:47] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun 4.18.0-15-generic #16-Ubuntu SMP Thu Feb 7 10:56:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux on an i7-6700 The flickering and the system crashes are gone, but the error still persits in the logs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [Lenovo ThinkPad X220] *ERROR* CPU pipe A FIFO underrun - Xorg glitches Status in linux package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-vid
[Kernel-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
That's an OOM problem. Just increase the reserved crashkernel memory size and test again, please. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: Won't Fix Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in initramfs-tools source package in Bionic: In Progress Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Invalid Status in initramfs-tools source package in Cosmic: In Progress Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: Invalid Status in initramfs-tools source package in Disco: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Invalid Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e4
[Kernel-packages] [Bug 1810457] Re: Update hisilicon SoC-specific drivers
Guess what! These changes... regressed my hardware. With 4.15.0-43-generic, I have functional networking via hns_enet_drv, and on 4.15.0-45-generic I have... no networking. Huawei TaiShan XR320 blade in Huawei TaiShan X6000 chassis. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810457 Title: Update hisilicon SoC-specific drivers Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] Drivers for the HiSilicon Hi1616 and Hi1620 SoCs continue to be under active development, including both hardware enablement and bug fix patches. With the amount of flux involved, identifying and cherry-picking individual patches would be more error prone then re-syncing with current upstream. [Test Case] The Ubuntu server certification suite, which includes network and storage tests. [Fix] Backport the localized driver changes up to v5.0-rc1. [Regression Risk] These changes are restricted to the hns and hisi_sas drivers, which only impact the D05 and D06 server development board platforms. To mitigate this risk, we have explicitly tested the proposed changes on these 2 platforms - changes are staged in ppa:pearl2-team/test. Of course, there is risk that these changes introduced regressions that our testing did not catch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
I've managed to verify this on kernel 4.4.0-143-generic, the problem
isn't reproducible anymore.
Worth noticing that when using the kernel 4.4.0-143 in both host and
guest, we cannot change MSR bit anymore from within the guest, so the
performance drop is not observed.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764956
Title:
Guests using IBRS incur a large performance penalty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
Fix Committed
Bug description:
[Impact]
the IBRS would be mistakenly enabled in the host when the switching
from an IBRS-enabled VM and that causes the performance overhead in
the host. The other condition could also mistakenly disables the IBRS
in VM when context-switching from the host. And this could be
considered a CVE host.
[Fix]
The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
x86_spec_ctrl_base by default is zero. Because the upstream
implementation is not equal to the Xenial's implementation. Upstream
doesn't use the IBRS as the formal fix. So, by default, it's zero.
On the other hand, after the VM exit, the SPEC_CTRL register also
needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
intercept is disabled by default in the hardware_setup(v4.4) and
vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
The v3.13 kernel hasn't been tested. However, the patch can be viewed
at:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
The v4.4 patch:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
[Test]
The patch has been tested on the 4.4.0-140.166 and works fine.
The reproducing environment:
Guest kernel version: 4.4.0-138.164
Host kernel version: 4.4.0-140.166
(host IBRS, guest IBRS)
- 1). (0, 1).
The case can be reproduced by the following instructions:
guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
1
host$ cat /proc/sys/kernel/ibrs_enabled
0
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
110001001010
Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
enabled.
host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
stress-ng: info: [11264] defaulting to a 86400 second run per stressor
stress-ng: info: [11264] dispatching hogs: 1 cpu
stress-ng: info: [11264] cache allocate: default cache size: 35840K
stress-ng: info: [11264] successful run completed in 33.48s
The host kernel didn't notice the IBRS bit is enabled. So, the situation
is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
And running the stress-ng is a pure userspace CPU capability
calculation. So, the performance downgrades to about 1/3. Without the
IBRS enabled, it needs about 10s.
- 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
The guest IBRS has been mistakenly disabled.
guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Seth, my only preference here is that the test cases be appropriate for what's being updated. If there are going to be updates affecting multiple series of chips, then I think the test case should also cover testing across multiple series. Otherwise, if that testing is onerous, I think withdrawing this SRU and changing only the firmware for the series we know is affected by this bug would be better. -- 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Committed Status in The Bionic Beaver: New Status in linux-firmware source package in Bionic: Incomplete Status in The Cosmic Cuttlefish: New Status in linux-firmware source package in Cosmic: Incomplete Bug description: SRU Justification: === [Impact] repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. [Fix] New iwlwifi firmware fix it. [Test] Bug reporter verified with positive result. [Regression Potential] Upstream fix, low risk. Bug reporter confirms fix. Original bug report: = Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0: 0x0501001C | hcmd Dec 13 11:53:36 james-x1 kernel: [ 856.845072] iwlwifi :02:00.0: 0x00023008 | isr0 Dec 13 11:53:36 james-x1 kernel: [ 856.845075] iwlwifi :02:00.0: 0x000D | isr1 Dec 13 11:53:36 james-x1 kernel: [ 856.845077] iwlwifi :02:00.0: 0x08001802 | isr2 Dec 13 11:53:36 james-x1 kernel: [ 856.845080] iwlwifi :02:00.0: 0x0041FDC0 | isr3 Dec 13 11:53:36 james-x1 kernel: [ 856.845082] iwlwifi :02:00.0: 0x | isr4 Dec 13 11:53:36 james-x1 kernel: [ 856.845084] iwlwifi :02:00.0: 0x00580118 | last cmd Id Dec 13 11:53:36 james-x1 kernel: [ 856.845087] iwlwifi :02:00.0: 0x | wait_event Dec 13 11:53:36 james-x1 kernel: [ 856.845089] iwlwifi :02:00.0: 0x76DD | l2p_control Dec 13 11:53:36 james-x1 kernel: [ 856.845091] iwlwifi :02:00.0: 0x0020 | l2p_duration Dec 13 11:53:36 james-x1 kernel: [ 856.845094] iwlwifi :02:00.0: 0x | l2p_mhvalid Dec 13 11:53:36 james-x1 kernel: [ 856.845096] iwlwifi :02:00.0: 0x00A0 | l2p_addr_match Dec 13 11:53:36 james-x1 kernel: [ 856.84
[Kernel-packages] [Bug 1811777] Re: Fix non-working pinctrl-intel
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811777 Title: Fix non-working pinctrl-intel Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Intel pinctrl doesn't work. There's a WWAN card needs to use pinctrl to reset itself after firmware update. Currently we can't use pinctrl to reset it. [Fix] Translate GPIO to pinctrl pins correctly. [Test] The WWAN reset function works once the fix is applied. [Regression Potential] Low. Limits to pinctrl-intel and it's in mainline for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1811777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594591] Re: Bluetooth audio isn't working properly!
I have this bluetooth headphone audio stutter issue on Ubuntu 18.04 amd_64 on a 2014 Macbook Pro 15" with the A2DP profile selected in Settings -> Sound. But the stutter disappears under "Headset Head Unit" profile. -- 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/1594591 Title: Bluetooth audio isn't working properly! Status in bluez package in Ubuntu: Confirmed Bug description: My bluetooth headset is connected fine but the sound keeps stuttering, then the sound completely disappears! I noticed that it only happens when wifi is enabled! I'm using Ubuntu 16.04 LTS | Broadcom driver ps: it works quite well with windows 10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1594591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817420] Re: Second battery is not shown
Interesting, I have a 2 batteries thinkpad. kinfocenter show 1 battery too. battery-applet show 2 batteries. Just like yours. But in dmesg, my laptop show 2 batteries. Your dmesg shows one: [2.825178] ACPI: Battery Slot [BAT0] (battery present) Your request is a kde stuff, beyond my ability. Install acpidump $sudo apt install acpica-tools In case If you still want to upload acpidump. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817420 Title: Second battery is not shown Status in linux package in Ubuntu: Incomplete Bug description: I have a PC with two batteries, but it seems kinfocenter only shows one of the two. It would be nice to see the remaining capacity of both. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: udippel1670 F pulseaudio /dev/snd/controlC1: udippel1670 F pulseaudio /dev/snd/pcmC0D3p: udippel1670 F...m pulseaudio /dev/snd/controlC0: udippel1670 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc InstallationDate: Installed on 2019-02-16 (6 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETA2W (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818219] Re: Lenovo T480 freezes after screen has been locked
Hi Jussi: It looks like a dc stat issue. Could you try 4.16 kernel? https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ If it confirms fixed, I will recompile a kernel for you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818219 Title: Lenovo T480 freezes after screen has been locked Status in linux package in Ubuntu: Confirmed Bug description: This has now happened multiple times. When I just lock my screen (I have one external monitor attached to my laptop via HDMI) and leave my laptop alone for a while, it has somehow frozen when I get back. I'm not sure how long it will take, but something like 30-60 mins perhaps. Either one or usually both screens are just black and the machine doesn't respond to mouse or anything (haven't tried to SSH to the laptop). If I just suspend the laptop everything always goes just fine and it always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5MX:pvrThinkPadT480:rvnLENOVO:rn20L5MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5MX dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817420] Re: Second battery is not shown
There is no acpidump, but I can show the tlp stat: +++ ThinkPad Battery Features tp-smapi = inactive (unsupported hardware) tpacpi-bat = active +++ ThinkPad Battery Status: BAT0 (Main / Internal) /sys/class/power_supply/BAT0/manufacturer = SANYO /sys/class/power_supply/BAT0/model_name = 00HW005 /sys/class/power_supply/BAT0/cycle_count= (not supported) /sys/class/power_supply/BAT0/energy_full_design = 35020 [mWh] /sys/class/power_supply/BAT0/energy_full= 31040 [mWh] /sys/class/power_supply/BAT0/energy_now = 31020 [mWh] /sys/class/power_supply/BAT0/power_now = 0 [mW] /sys/class/power_supply/BAT0/status = Unknown (threshold effective) tpacpi-bat.BAT0.startThreshold = 96 [%] tpacpi-bat.BAT0.stopThreshold =100 [%] tpacpi-bat.BAT0.forceDischarge = 0 Charge = 99.9 [%] Capacity= 88.6 [%] +++ ThinkPad Battery Status: BAT1 (Ultrabay / Slice / Replaceable) /sys/class/power_supply/BAT1/manufacturer = LGC /sys/class/power_supply/BAT1/model_name = 00HW006 /sys/class/power_supply/BAT1/cycle_count= (not supported) /sys/class/power_supply/BAT1/energy_full_design = 26170 [mWh] /sys/class/power_supply/BAT1/energy_full= 17610 [mWh] /sys/class/power_supply/BAT1/energy_now = 15580 [mWh] /sys/class/power_supply/BAT1/power_now = 11307 [mW] /sys/class/power_supply/BAT1/status = Discharging tpacpi-bat.BAT1.startThreshold = 96 [%] tpacpi-bat.BAT1.stopThreshold =100 [%] tpacpi-bat.BAT1.forceDischarge = 0 Charge = 88.5 [%] Capacity= 67.3 [%] +++ Charge total= 95.8 [%] $ acpidump acpidump: command not found I also attach a screenshot, showing one battery in kinfocenter, and the two batteries on the battery-applet. ** Attachment added: "2 batteries in the battery widget and one in kinfocenter" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817420/+attachment/5242650/+files/Screenshot_20190301_181345.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817420 Title: Second battery is not shown Status in linux package in Ubuntu: Incomplete Bug description: I have a PC with two batteries, but it seems kinfocenter only shows one of the two. It would be nice to see the remaining capacity of both. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: udippel1670 F pulseaudio /dev/snd/controlC1: udippel1670 F pulseaudio /dev/snd/pcmC0D3p: udippel1670 F...m pulseaudio /dev/snd/controlC0: udippel1670 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc InstallationDate: Installed on 2019-02-16 (6 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETA2W (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO To manage n
[Kernel-packages] [Bug 1814747] Re: linux-oracle: 4.15.0-1009.11~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1814747 Title: linux-oracle: 4.15.0-1009.11~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Testing phase-changed: Tuesday, 26. February 2019 14:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817420] Re: Second battery is not shown
>From dmesg, only one battery exists. If you have 2 batteries inside, please upload acpidump. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817420 Title: Second battery is not shown Status in linux package in Ubuntu: Incomplete Bug description: I have a PC with two batteries, but it seems kinfocenter only shows one of the two. It would be nice to see the remaining capacity of both. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: udippel1670 F pulseaudio /dev/snd/controlC1: udippel1670 F pulseaudio /dev/snd/pcmC0D3p: udippel1670 F...m pulseaudio /dev/snd/controlC0: udippel1670 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc InstallationDate: Installed on 2019-02-16 (6 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20CHS10P02 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N17ETA2W (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CHS10P02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 11 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone: dmi.product.family: ThinkPad Helix 2nd dmi.product.name: 20CHS10P02 dmi.product.version: ThinkPad Helix 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818126] Re: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1818200 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1814749 - phase: Ready for Packaging - phase-changed: Thursday, 28. February 2019 18:36 UTC + phase: Testing + phase-changed: Friday, 01. March 2019 15:44 UTC reason: - prepare-package: Pending -- version not specified + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: Pending -- snap not in 18/beta channel + snap-release-to-edge: Pending -- snap not in 18/edge channel + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1818126 Title: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1818200 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1814749 phase: Testing phase-changed: Friday, 01. March 2019 15:44 UTC reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-aws (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
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/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
Fix Committed
Status in linux-azure source package in Cosmic:
In Progress
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
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:12:54 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/1812624/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818238] Re: fib_tests.sh net selftest is flaky when running carrier tests
Not much luck on 4.19 either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818238 Title: fib_tests.sh net selftest is flaky when running carrier tests Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The kernel net selftests include a fib_rules.sh that tests fib rules after carrier off. That test is flaky, which will cause false failures during ADT and SRU tests. [Test case] The carrier test has been run on a loop and the failure was noticed. After the fix, the failure does not appear. [Regression potential] This fix only applies to the selftests, not the kernel itself. The regression potential would be tests failing when they were not, but no regressions to users themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818238] Re: fib_tests.sh net selftest is flaky when running carrier tests
For some reason, I can't really reproduce the failure on cosmic 4.18 kernel, only on 5.0. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818238 Title: fib_tests.sh net selftest is flaky when running carrier tests Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The kernel net selftests include a fib_rules.sh that tests fib rules after carrier off. That test is flaky, which will cause false failures during ADT and SRU tests. [Test case] The carrier test has been run on a loop and the failure was noticed. After the fix, the failure does not appear. [Regression potential] This fix only applies to the selftests, not the kernel itself. The regression potential would be tests failing when they were not, but no regressions to users themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
** Changed in: linux-kvm (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux-kvm (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
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/1812624
Title:
PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option
was expected to be set in C-KVM
Status in ubuntu-kernel-tests:
In Progress
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-aws source package in Cosmic:
In Progress
Status in linux-azure source package in Cosmic:
In Progress
Status in linux-kvm source package in Cosmic:
Fix Committed
Status in linux-aws source package in Disco:
In Progress
Status in linux-azure source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
Issue reported by the kernel-security test:
==
FAIL: test_420_config_page_poisoning (__main__.KernelSecurityConfigTest)
Ensure page poisoning is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2676, in
test_420_config_page_poisoning
self.assertKernelConfig('PAGE_POISONING', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING option was expected to be set in the kernel
config
==
FAIL: test_421_config_page_poisoning_no_sanity
(__main__.KernelSecurityConfigTest)
Ensure page poisoning allocation sanity checking is disabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2694, in
test_421_config_page_poisoning_no_sanity
self.assertKernelConfig('PAGE_POISONING_NO_SANITY', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_NO_SANITY option was expected to be set in
the kernel config
==
FAIL: test_421_config_page_poisoning_zero
(__main__.KernelSecurityConfigTest)
Ensure page poisoning to zero is enabled (LP: #1783651)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2685, in
test_421_config_page_poisoning_zero
self.assertKernelConfig('PAGE_POISONING_ZERO', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: PAGE_POISONING_ZERO option was expected to be set in the
kernel config
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:12:54 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/1812624/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818238] 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 1818238 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818238 Title: fib_tests.sh net selftest is flaky when running carrier tests Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The kernel net selftests include a fib_rules.sh that tests fib rules after carrier off. That test is flaky, which will cause false failures during ADT and SRU tests. [Test case] The carrier test has been run on a loop and the failure was noticed. After the fix, the failure does not appear. [Regression potential] This fix only applies to the selftests, not the kernel itself. The regression potential would be tests failing when they were not, but no regressions to users themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu
Launchpad has imported 13 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199035.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2018-03-06T21:09:45+00:00 mathieutournier wrote:
Created attachment 274593
dmesg
Hi,
I'm currently running ubuntu 18.04 with a 4.15 kernel and i can observe very
high cpu usage to the systemd-udevd deamon.
removing the rule :
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01",
ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c",
ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
Solved the high CPU usage eventhough my bluetooth card is not available
anymore (as not in hci mode)
It seems that the command hid2hci creates a bind/unbind loop in udev
that is looping trying to set the device in hci mode. (that what udevadm
monitor seems to show, looping from bind to unbind for the device)
I suspect a0085f2510e8976614ad8f766b209448b385492f introduced a
regression (i have not tried to revert it yet).
Please not that there also seem to be a bug in hid2hci.c from bluez l148 :
if (err == 0) {
err = -1;
errno = EALREADY;
}
Correcting this and recompile bluez desn't solve the issue as cpu usage remains
very high.
Using a 4.13 kernel result in a normal CPU usage, this seems a
regression in 4.14.
Other people seems to have the same issue, here is a bug report related to this
:
https://dev.solus-project.com/T5224
Thanks a lot for your support,
Mathieu Tournier
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/0
On 2018-05-04T05:57:10+00:00 boro wrote:
I have the very same problem using the same distro (Ubuntu 18.04,
64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or
removing the aforementioned rule solves the problem but leaves BT
unusable.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/1
On 2018-05-09T23:02:06+00:00 lucent wrote:
Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of
BCM2046 Bluetooth)
Bus 001 Device 004: ID 0a5c: Broadcom Corp.
Linux zontar 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64
GNU/Linux
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0
...repeating...
15632 root 20 0 233136 186656 2664 R 94.1% 4.7% 62:14.67
systemd-udevd
16222 root 20 0 88252 2432 1888 R 35.3% 0.1% 25:21.87
systemd-udevd
Looks like same problem affects this Dell Precision M6500 laptop.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/2
On 2018-05-20T07:57:41+00:00 f.dittmer wrote:
I observed the high cpu usage after upgrading from udev-233 to
udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use
newer kernels (currently running 4.15.18) without any problems.
Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as
mentioned above.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/3
On 2018-06-13T16:50:40+00:00 rickfharris wrote:
As per https://patchwork.kernel.org/patch/10384111/ editing
97-hid2hci.rules as follows works around the new uevents added to the
kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
-ACTION=="remove", GOTO="hid2hci_end"
+ACTION!="add", GOTO="hid2hci_end"
Bluetooth now works with kernels above and below 4.14.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788018/comments/4
On 2018-06-14T00:32:13+00:00 ri
[Kernel-packages] [Bug 1818237] [NEW] Xenial update: 4.4.171 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: 4.4.171 upstream stable release from git://git.kernel.org/ Linux 4.4.171 sunrpc: use-after-free in svc_process_common() ext4: fix a potential fiemap/page fault deadlock w/ inline_data crypto: cts - fix crash on short inputs i2c: dev: prevent adapter retries and timeout being set as minus value ACPI: power: Skip duplicate power resource references in _PRx PCI: altera: Move retrain from fixup to altera_pcie_host_init() PCI: altera: Rework config accessors for use without a struct pci_bus PCI: altera: Poll for link training status after retraining the link PCI: altera: Poll for link up status after retraining the link PCI: altera: Check link status before retrain link PCI: altera: Reorder read/write functions PCI: altera: Fix altera_pcie_link_is_up() slab: alien caches must not be initialized if the allocation of the alien cache failed USB: Add USB_QUIRK_DELAY_CTRL_MSG quirk for Corsair K70 RGB USB: storage: add quirk for SMI SM3350 USB: storage: don't insert sane sense for SPC3+ when bad sense specified usb: cdc-acm: send ZLP for Telit 3G Intel based modems cifs: Fix potential OOB access of lock element array CIFS: Do not hide EINTR after sending network packets btrfs: tree-checker: Fix misleading group system information btrfs: tree-checker: Check level for leaves and nodes btrfs: Verify that every chunk has corresponding block group at mount time btrfs: Check that each block group has corresponding chunk at mount time btrfs: validate type when reading a chunk btrfs: tree-checker: Detect invalid and empty essential trees btrfs: tree-checker: Verify block_group_item btrfs: tree-check: reduce stack consumption in check_dir_item btrfs: tree-checker: use %zu format string for size_t btrfs: tree-checker: Add checker for dir item btrfs: tree-checker: Fix false panic for sanity test btrfs: tree-checker: Enhance btrfs_check_node output btrfs: Move leaf and node validation checker to tree-checker.c btrfs: Add checker for EXTENT_CSUM btrfs: Add sanity check for EXTENT_DATA when reading out leaf btrfs: Check if item pointer overlaps with the item itself btrfs: Refactor check_leaf function for later expansion btrfs: struct-funcs, constify readers Btrfs: fix emptiness check for dirtied extent buffers at check_leaf() Btrfs: memset to avoid stale content in btree leaf Btrfs: kill BUG_ON in run_delayed_tree_ref Btrfs: improve check_node to avoid reading corrupted nodes Btrfs: memset to avoid stale content in btree node block Btrfs: fix BUG_ON in btrfs_mark_buffer_dirty Btrfs: check btree node's nritems Btrfs: detect corruption when non-root leaf has zero item Btrfs: fix em leak in find_first_block_group Btrfs: check inconsistence between chunk and block group Btrfs: add validadtion checks for chunk loading btrfs: Enhance chunk validation check btrfs: cleanup, stop casting for extent_map->lookup everywhere ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** 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 ** Summary changed: - Xenial update: v4.4.171 upstream stable release + Xenial update: 4.4.171 upstream stable release ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, 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: + 4.4.171 upstream stable release + from git://git.kernel.org/ -v4.4.171 upstream stable release -
[Kernel-packages] [Bug 1818238] [NEW] fib_tests.sh net selftest is flaky when running carrier tests
Public bug reported: [Impact] The kernel net selftests include a fib_rules.sh that tests fib rules after carrier off. That test is flaky, which will cause false failures during ADT and SRU tests. [Test case] The carrier test has been run on a loop and the failure was noticed. After the fix, the failure does not appear. [Regression potential] This fix only applies to the selftests, not the kernel itself. The regression potential would be tests failing when they were not, but no regressions to users themselves. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818238 Title: fib_tests.sh net selftest is flaky when running carrier tests Status in linux package in Ubuntu: New Bug description: [Impact] The kernel net selftests include a fib_rules.sh that tests fib rules after carrier off. That test is flaky, which will cause false failures during ADT and SRU tests. [Test case] The carrier test has been run on a loop and the failure was noticed. After the fix, the failure does not appear. [Regression potential] This fix only applies to the selftests, not the kernel itself. The regression potential would be tests failing when they were not, but no regressions to users themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)
*** This bug is a duplicate of bug 1818049 *** https://bugs.launchpad.net/bugs/1818049 ** This bug has been marked a duplicate of bug 1818049 virtualbox dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vend
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@dustya Thanks a lot for the feedback. I think that I will install both operating systems on the laptop, and check what happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818148] Re: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed)
Am I correct in saying that this is probably due to the kernel module not being built correctly? I'm marking as 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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtu
[Kernel-packages] [Bug 1813955] Re: CONFIG_TEST_BPF is disabled
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813955 Title: CONFIG_TEST_BPF is disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] Our bpf testing will fail or be skipped without notice. So, real bpf failures might end up being missed. [Test case] Both ADT and SRU will end up testing the built module. [Regression potential] Our tests will start showing real failures we don't want to miss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815234] Re: Bionic update: upstream stable patchset 2019-02-08
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815234
Title:
Bionic update: upstream stable patchset 2019-02-08
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-02-08 (ported from v4.14.60 and v4.17.12)
from git://git.kernel.org/
fork: unconditionally clear stack on fork
spi: spi-s3c64xx: Fix system resume support
Input: elan_i2c - add ACPI ID for lenovo ideapad 330
Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
kvm, mm: account shadow page tables to kmemcg
delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
tracing: Fix double free of event_trigger_data
tracing: Fix possible double free in event_enable_trigger_func()
kthread, tracing: Don't expose half-written comm when creating kthreads
tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
tracing: Quiet gcc warning about maybe unused link variable
arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups
mlxsw: spectrum_switchdev: Fix port_vlan refcounting
kcov: ensure irq code sees a valid area
xen/netfront: raise max number of slots in xennet_get_responses()
skip LAYOUTRETURN if layout is invalid
ALSA: emu10k1: add error handling for snd_ctl_add
ALSA: fm801: add error handling for snd_ctl_add
NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
vfio: platform: Fix reset module leak in error path
vfio/mdev: Check globally for duplicate devices
vfio/type1: Fix task tracking for QEMU vCPU hotplug
kernel/hung_task.c: show all hung tasks before panic
mm: /proc/pid/pagemap: hide swap entries from unprivileged users
mm: vmalloc: avoid racy handling of debugobjects in vunmap
mm/slub.c: add __printf verification to slab_err()
rtc: ensure rtc_set_alarm fails when alarms are not supported
perf tools: Fix pmu events parsing rule
netfilter: ipset: forbid family for hash:mac sets
netfilter: ipset: List timing out entries with "timeout 1" instead of zero
irqchip/ls-scfg-msi: Map MSIs in the iommu
watchdog: da9063: Fix updating timeout value
printk: drop in_nmi check from printk_safe_flush_on_panic()
bpf, arm32: fix inconsistent naming about emit_a32_lsr_{r64,i64}
ceph: fix alignment of rasize
e1000e: Ignore TSYNCRXCTL when getting I219 clock attributes
powerpc/lib: Adjust .balign inside string functions for PPC32
powerpc/64s: Add barrier_nospec
powerpc/eeh: Fix use-after-release of EEH driver
hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
powerpc/64s: Fix compiler store ordering to SLB shadow area
RDMA/mad: Convert BUG_ONs to error flows
lightnvm: pblk: warn in case of corrupted write buffer
netfilter: nf_tables: check msg_type before nft_trans_set(trans)
pnfs: Don't release the sequence slot until we've processed layoutget on open
disable loading f2fs module on PAGE_SIZE > 4KB
f2fs: fix error path of move_data_page
f2fs: fix to don't trigger writeback during recovery
f2fs: fix to wait page writeback during revoking atomic write
f2fs: Fix deadlock in shutdown ioctl
f2fs: fix to detect failure of dquot_initialize
f2fs: fix race in between GC and atomic open
block, bfq: remove wrong lock in bfq_requests_merged
usbip: usbip_detach: Fix memory, udev context and udev leak
usbip: dynamically allocate idev by nports found in sysfs
perf/x86/intel/uncore: Correct fixed counter index check in generic code
perf/x86/intel/uncore: Correct fixed counter index check for NHM
selftests/intel_pstate: Improve test, minor fixes
selftests: memfd: return Kselftest Skip code for skipped tests
selftests: intel_pstate: return Kselftest Skip code for skipped tests
PCI: Fix devm_pci_alloc_host_bridge() memory leak
iwlwifi: pcie: fix race in Rx buffer allocator
Bluetooth: hci_qca: Fix "Sleep inside atomic section" warning
Bluetooth: btusb: Add a new Realtek 8723DE ID 2ff8:b011
ASoC: dpcm: fix BE dai not hw_free and shutdown
mfd: cros_ec: Fail ear
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
> * If I understand correctly, the bug does not occur in Ubuntu 18.10. The user can switch seamlessly between using the Intel or the Nvidia discrete graphics card. Is this correct? @jespestana No, this bug is affecting me on 18.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814813] Re: Bionic update: upstream stable patchset 2019-02-05
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814813 Title: Bionic update: upstream stable patchset 2019-02-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-02-05 (ported from v4.14.59 and v4.17.11) from git://git.kernel.org/ MIPS: ath79: fix register address in ath79_ddr_wb_flush() MIPS: Fix off-by-one in pci_resource_to_user() xen/PVH: Set up GS segment for stack canary drm/nouveau/drm/nouveau: Fix runtime PM leak in nv50_disp_atomic_commit() drm/nouveau: Set DRIVER_ATOMIC cap earlier to fix debugfs bonding: set default miimon value for non-arp modes if not set ip: hash fragments consistently ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull net/mlx4_core: Save the qpn from the input modifier in RST2INIT wrapper net: skb_segment() should not return NULL net/mlx5: Adjust clock overflow work period net/mlx5e: Don't allow aRFS for encapsulated packets net/mlx5e: Fix quota counting in aRFS expire flow net/ipv6: Fix linklocal to global address with VRF multicast: do not restore deleted record source filter mode to new one net: phy: consider PHY_IGNORE_INTERRUPT in phy_start_aneg_priv sock: fix sg page frag coalescing in sk_alloc_sg rtnetlink: add rtnl_link_state check in rtnl_configure_link vxlan: add new fdb alloc and create helpers vxlan: make netlink notify in vxlan_fdb_destroy optional vxlan: fix default fdb entry netlink notify ordering during netdev create tcp: fix dctcp delayed ACK schedule tcp: helpers to send special DCTCP ack tcp: do not cancel delay-AcK on DCTCP special ACK tcp: do not delay ACK in DCTCP upon CE status change staging: speakup: fix wraparound in uaccess length check usb: cdc_acm: Add quirk for Castles VEGA3000 usb: core: handle hub C_PORT_OVER_CURRENT condition usb: dwc2: Fix DMA alignment to start at allocated boundary usb: gadget: f_fs: Only return delayed status when len is 0 driver core: Partially revert "driver core: correct device's shutdown order" can: xilinx_can: fix RX loop if RXNEMP is asserted without RXOK can: xilinx_can: fix power management handling can: xilinx_can: fix recovery from error states not being propagated can: xilinx_can: fix device dropping off bus on RX overrun can: xilinx_can: keep only 1-2 frames in TX FIFO to fix TX accounting can: xilinx_can: fix incorrect clear of non-processed interrupts can: xilinx_can: fix RX overflow interrupt not being enabled can: peak_canfd: fix firmware < v3.3.0: limit allocation to 32-bit DMA addr only can: m_can.c: fix setup of CCCR register: clear CCCR NISO bit before checking can.ctrlmode turn off -Wattribute-alias net-next/hinic: fix a problem in hinic_xmit_frame() net/mlx5e: Refine ets validation function nfp: flower: ensure dead neighbour entries are not offloaded usb: gadget: Fix OS descriptors support ACPICA: AML Parser: ignore dispatcher error status during table load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818126] Re: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1818126 Title: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1818200 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1814749 phase: Ready for Packaging phase-changed: Thursday, 28. February 2019 18:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818228] [NEW] thunderbolt
Public bug reported: [ 51.501462] [ cut here ] [ 51.501465] thunderbolt :08:00.0: interrupt for TX ring 0 is already disabled [ 51.501480] WARNING: CPU: 4 PID: 82 at /build/linux-uQJ2um/linux-4.15.0/drivers/thunderbolt/nhi.c:106 ring_interrupt_active+0x20c/0x270 [thunderbolt] [ 51.501481] Modules linked in: rfcomm ccm thunderbolt cmac bnep arc4 snd_hda_codec_hdmi nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch dell_wmi dell_laptop dell_smbios wmi_bmof intel_wmi_thunderbolt intel_rapl mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp dell_wmi_descriptor dcdbas kvm_intel dell_smm_hwmon kvm irqbypass snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hda_core pcbc snd_hwdep snd_pcm ath10k_pci aesni_intel ath10k_core aes_x86_64 crypto_simd glue_helper cryptd snd_seq_midi ath uvcvideo intel_cstate snd_seq_midi_event snd_rawmidi intel_rapl_perf mac80211 snd_seq videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_device snd_timer serio_raw videobuf2_core cdc_ether btusb usbnet videodev btrtl snd btbcm idma64 btintel [ 51.501517] r8152 virt_dma media soundcore joydev rtsx_pci_ms mii input_leds cfg80211 bluetooth memstick ecdh_generic mei_me intel_lpss_pci processor_thermal_device mei shpchp intel_soc_dts_iosf intel_lpss intel_pch_thermal nvidia_uvm(POE) int3400_thermal int3403_thermal int340x_thermal_zone wmi acpi_thermal_rel mac_hid intel_hid acpi_pad sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid ses enclosure scsi_transport_sas uas usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc fb_sys_fops ahci nvme ipmi_devintf psmouse drm nvme_core rtsx_pci libahci ipmi_msghandler i2c_hid hid video [ 51.501552] CPU: 4 PID: 82 Comm: kworker/u16:1 Tainted: PW OE 4.15.0-45-generic #48-Ubuntu [ 51.501553] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.12.1 10/02/2018 [ 51.501556] Workqueue: kacpi_hotplug acpi_hotplug_work_fn [ 51.501561] RIP: 0010:ring_interrupt_active+0x20c/0x270 [thunderbolt] [ 51.501562] RSP: 0018:9eb4c1befb38 EFLAGS: 00010082 [ 51.501563] RAX: RBX: RCX: 0006 [ 51.501564] RDX: 0007 RSI: 0092 RDI: 92e47e516490 [ 51.501565] RBP: 9eb4c1befb70 R08: 0001 R09: 0529 [ 51.501566] R10: 0040 R11: R12: c1d90a1d [ 51.501567] R13: 00038200 R14: 92e4641d3c00 R15: c1d90a14 [ 51.501568] FS: () GS:92e47e50() knlGS: [ 51.501569] CS: 0010 DS: ES: CR0: 80050033 [ 51.501570] CR2: 1fbc9e7103f8 CR3: 2660a004 CR4: 003606e0 [ 51.501570] Call Trace: [ 51.501575] tb_ring_stop+0x109/0x160 [thunderbolt] [ 51.501578] tb_ctl_stop+0x45/0xc0 [thunderbolt] [ 51.501582] tb_domain_remove+0x42/0x70 [thunderbolt] [ 51.501585] nhi_remove+0x4b/0x60 [thunderbolt] [ 51.501588] pci_device_remove+0x3e/0xb0 [ 51.501590] device_release_driver_internal+0x15b/0x240 [ 51.501592] device_release_driver+0x12/0x20 [ 51.501594] pci_stop_bus_device+0x7f/0xa0 [ 51.501595] pci_stop_and_remove_bus_device+0x12/0x20 [ 51.501597] trim_stale_devices+0x11d/0x150 [ 51.501598] trim_stale_devices+0xa9/0x150 [ 51.501599] trim_stale_devices+0xbb/0x150 [ 51.501600] ? get_slot_status+0xa2/0x100 [ 51.501601] acpiphp_check_bridge.part.7+0x100/0x140 [ 51.501602] acpiphp_hotplug_notify+0x18e/0x220 [ 51.501603] ? free_bridge+0x100/0x100 [ 51.501605] acpi_device_hotplug+0xa4/0x4b0 [ 51.501607] acpi_hotplug_work_fn+0x1e/0x30 [ 51.501609] process_one_work+0x1de/0x410 [ 51.501610] worker_thread+0x32/0x410 [ 51.501612] kthread+0x121/0x140 [ 51.501613] ? process_one_work+0x410/0x410 [ 51.501615] ? kthread_create_worker_on_cpu+0x70/0x70 [ 51.501617] ret_from_fork+0x35/0x40 [ 51.501618] Code: 00 48 89 55 c8 44 89 45 d4 e8 21 a0 8c ee 44 8b 45 d4 48 8b 55 c8 4d 89 f9 4c 89 e1 48 89 c6 48 c7 c7 38 12 d9 c1 e8 b4 d8 30 ee <0f> 0b e9 36 ff ff ff 41 0f b6 46 78 d3 e0 09 c7 e9 cd fe ff ff [ 51.501644] ---[ end trace dbb8a6822d824854 ]--- ** Affects: thunderbolt-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1818228 Title: thunderbolt Status in thunderbolt-tools package in Ubuntu: New Bug description: [ 51.501462] [ cut here ] [ 51.501465] thunderbolt :08:00.0: interrupt for TX ring 0 is already disabled [ 51.501480] WARNING: CPU: 4 PID: 82 at /build/linux-uQJ2um/linux-4.15.0/drivers
[Kernel-packages] [Bug 1818126] Re: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1818126 Title: linux-azure: 4.18.0-1013.13~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1818200 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1814749 phase: Ready for Packaging phase-changed: Thursday, 28. February 2019 18:36 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Friday, 01. March 2019 11:34 UTC + phase: Ready for Testing + phase-changed: Friday, 01. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing 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/1814645 Title: linux: 3.13.0-166.216 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Friday, 01. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814749 - phase: Promote to Proposed - phase-changed: Friday, 01. March 2019 09:36 UTC + phase: Testing + phase-changed: Friday, 01. March 2019 12:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1818128 Title: linux-azure: 4.18.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814749 phase: Testing phase-changed: Friday, 01. March 2019 12:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)
** No longer affects: linux (Ubuntu Xenial) ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804588 Title: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] On new systems that facilitate s2idle, we observed the power consumption raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF. Short idle: 6 Long idle: 2 S2I: 4.8 [Fix] Windows doesn't put nvme to D3 in modern standby, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on the new Intel NVMe, it fixes the power consumption issue with no regression. And the power consumption decreases to 2.8W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730782] Re: [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL
Hi @quanxian. What commits are these? Do you want these on bionic 4.15? Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730782 Title: [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL Status in intel: Fix Released Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Workload slows down for default sampling cycles in KNL. There are some processing in perf that's single threaded and bottlenecked when number of cores really go up. A second issue is that things slow down when we issue perf record – workload vs perf record -a – workload Patch is submitted for review https://www.spinics.net/lists/kernel/msg2552460.html https://www.spinics.net/lists/kernel/msg2552461.html https://www.spinics.net/lists/kernel/msg2552462.html https://www.spinics.net/lists/kernel/msg2552463.html Target kernel: 5.2 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy
** Description changed: + [Impact] + + udev fails to rename a new interface when a VF is added due to a race + between the kernel and userspace. + + It's desirable to get a consistent and predictable name, as otherwise + any persistent configuration in userspace can't be applied properly on + the Virtual Function that gets hot plugged in. + + [Test Case] + Host has a QEMU/KVM setup with standby virtio-net [1]: # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on Guest is loaded with Xenial Xerus (16.04.5), vsbalakr@ubuntu-16:~$ uname -a Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux vsbalakr@ubuntu-16:~$ cat /proc/version_signature Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18 vsbalakr@ubuntu-16:~$ cat /etc/os*release NAME="Ubuntu" VERSION="16.04.5 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.5 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial - vsbalakr@ubuntu-16:~$ + vsbalakr@ubuntu-16:~$ ens3 is the master interface of net_failover, while ens3nsby is its standby slave [2]: vsbalakr@ubuntu-16:~$ ip a sh 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo -valid_lft forever preferred_lft forever - inet6 ::1/128 scope host -valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff - inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3 -valid_lft forever preferred_lft forever - inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link - valid_lft forever preferred_lft forever + link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff + inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3 + valid_lft forever preferred_lft forever + inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link + valid_lft forever preferred_lft forever 3: ens3nsby: mtu 1500 qdisc pfifo_fast master ens3 state UP group default qlen 1000 - link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff - inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby -valid_lft 2154sec preferred_lft 2154sec - inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link - valid_lft forever preferred_lft forever + link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff + inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby + valid_lft 2154sec preferred_lft 2154sec + inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link + valid_lft forever preferred_lft forever Now we hot plug a Virtual Function (with MAC set to same address d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console: (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0 (qemu) VF now shows up in guest as "eth0" instead of the expected "ens4": vsbalakr@ubuntu-16:~$ ip a sh 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - inet 127.0.0.1/8 scope host lo -valid_lft forever preferred_lft forever - inet6 ::1/128 scope host -valid_lft forever preferred_lft forever + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 + inet 127.0.0.1/8 scope host lo + valid_lft forever preferred_lft forever + inet6 ::1/128 scope host + valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff - inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3 -valid_lft forever preferred_lft forever - inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary dynamicvalid_lft 604753sec preferred_lft 86209sec - inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr dynamicvalid_lft 2591959sec preferred_lft 604759sec - inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link -valid_lft forever preferred_lft forever + link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff + inet 10.211.15.21/21 brd 10.211.1
[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-meta (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-meta-hwe (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: apt (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: In Progress Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: In Progress Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kern
[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-166.216 /trusty-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814645 Title: linux: 3.13.0-166.216 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 01. March 2019 11:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy
** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oracle (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-oracle (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1815268 Title: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy Status in linux package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oracle source package in Bionic: In Progress Bug description: Host has a QEMU/KVM setup with standby virtio-net [1]: # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on Guest is loaded with Xenial Xerus (16.04.5), vsbalakr@ubuntu-16:~$ uname -a Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux vsbalakr@ubuntu-16:~$ cat /proc/version_signature Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18 vsbalakr@ubuntu-16:~$ cat /etc/os*release NAME="Ubuntu" VERSION="16.04.5 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.5 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial vsbalakr@ubuntu-16:~$ ens3 is the master interface of net_failover, while ens3nsby is its standby slave [2]: vsbalakr@ubuntu-16:~$ ip a sh 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link valid_lft forever preferred_lft forever 3: ens3nsby: mtu 1500 qdisc pfifo_fast master ens3 state UP group default qlen 1000 link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby valid_lft 2154sec preferred_lft 2154sec inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link valid_lft forever preferred_lft forever Now we hot plug a Virtual Function (with MAC set to same address d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console: (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0 (qemu) VF now shows up in guest as "eth0" instead of the expected "ens4": vsbalakr@ubuntu-16:~$ ip a sh 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3 valid_lft forever preferred_lft forever inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary dynamicvalid_lft 604753sec preferred_lft 86209sec inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr dynamicvalid_lft 2591959sec preferred_lft 604759sec inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link valid_lft forever preferred_lft forever 3: ens3nsby: mtu 1500 qdisc pfifo_fast master ens3 state UP group default qlen 1000 link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby valid_lft 2072sec preferred_lft 2072sec inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link valid_lft
[Kernel-packages] [Bug 1818219] Re: Lenovo T480 freezes after screen has been locked
** Description changed: - It has now happened multiple times that when I just lock my screen (I - have one external monitor attached to my laptop via HDMI) my laptop has - somehow frozen when I get back. I'm not sure how long it will take, but - 30-60 min perhaps. Either one or usually both screens are just black and - the machine doesn't respond to mouse or anything. + This has now happened multiple times. When I just lock my screen (I have + one external monitor attached to my laptop via HDMI) and leave my laptop + alone for a while, it has somehow frozen when I get back. I'm not sure + how long it will take, but something like 30-60 mins perhaps. Either one + or usually both screens are just black and the machine doesn't respond + to mouse or anything (haven't tried to SSH to the laptop). - If I just suspend the laptop everything always goes just fine. + If I just suspend the laptop everything always goes just fine and it + always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio - /dev/snd/controlC0: jussili2985 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio + /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: - linux-restricted-modules-4.15.0-42-generic N/A - linux-backports-modules-4.15.0-42-generic N/A - linux-firmware 1.173.2 + linux-restricted-modules-4.15.0-42-generic N/A + linux-backports-modules-4.15.0-42-generic N/A + linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5MX:pvrThinkPadT480:rvnLENOVO:rn20L5MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5MX dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818219 Title: Lenovo T480 freezes after screen has been locked Status in linux package in Ubuntu: Confirmed Bug description: This has now happened multiple times. When I just lock my screen (I have one external monitor attached to my laptop via HDMI) and leave my laptop alone for a while, it has somehow frozen when I get back. I'm not sure how long it will take, but something like 30-60 mins perhaps. Either one or usually both screens are just black and the machine doesn't respond to mouse or anything (haven't tried to SSH to the laptop). If I just suspend the laptop everything always goes just fine and it always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bi
[Kernel-packages] [Bug 1818128] Re: linux-azure: 4.18.0-1013.13 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814749 phase: Promote to Proposed phase-changed: Friday, 01. March 2019 09:36 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1818128 Title: linux-azure: 4.18.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814749 phase: Promote to Proposed phase-changed: Friday, 01. March 2019 09:36 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1818128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3462 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818219] 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/1818219 Title: Lenovo T480 freezes after screen has been locked Status in linux package in Ubuntu: Confirmed Bug description: This has now happened multiple times. When I just lock my screen (I have one external monitor attached to my laptop via HDMI) and leave my laptop alone for a while, it has somehow frozen when I get back. I'm not sure how long it will take, but something like 30-60 mins perhaps. Either one or usually both screens are just black and the machine doesn't respond to mouse or anything (haven't tried to SSH to the laptop). If I just suspend the laptop everything always goes just fine and it always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5MX:pvrThinkPadT480:rvnLENOVO:rn20L5MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5MX dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Ready for Testing - phase-changed: Tuesday, 26. February 2019 18:32 UTC + phase: Testing + phase-changed: Friday, 01. March 2019 11:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing 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/1814645 Title: linux: 3.13.0-166.216 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 01. March 2019 11:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818219] Re: Lenovo T480 freezes after screen has been locked
I attached my kern.log. Today (Mar 1 2019) this issue occurred sometime between 12:00 and 13:00. I can see things like these, but don't know if they are related: Mar 1 12:29:25 T480 kernel: [50812.073470] WARNING: CPU: 0 PID: 2861 at /build/linux-Y38gIP/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x181/0x190 [drm] Mar 1 12:29:25 T480 kernel: [50812.073537] CPU: 0 PID: 2861 Comm: Xorg Tainted: GW O 4.15.0-42-generic #45-Ubuntu ** Attachment added: "Kernel log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818219/+attachment/5242595/+files/kern.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/1818219 Title: Lenovo T480 freezes after screen has been locked Status in linux package in Ubuntu: Confirmed Bug description: This has now happened multiple times. When I just lock my screen (I have one external monitor attached to my laptop via HDMI) and leave my laptop alone for a while, it has somehow frozen when I get back. I'm not sure how long it will take, but something like 30-60 mins perhaps. Either one or usually both screens are just black and the machine doesn't respond to mouse or anything (haven't tried to SSH to the laptop). If I just suspend the laptop everything always goes just fine and it always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5MX:pvrThinkPadT480:rvnLENOVO:rn20L5MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5MX dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818219] [NEW] Lenovo T480 freezes after screen has been locked
Public bug reported: This has now happened multiple times. When I just lock my screen (I have one external monitor attached to my laptop via HDMI) and leave my laptop alone for a while, it has somehow frozen when I get back. I'm not sure how long it will take, but something like 30-60 mins perhaps. Either one or usually both screens are just black and the machine doesn't respond to mouse or anything (haven't tried to SSH to the laptop). If I just suspend the laptop everything always goes just fine and it always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5MX:pvrThinkPadT480:rvnLENOVO:rn20L5MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5MX dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug 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/1818219 Title: Lenovo T480 freezes after screen has been locked Status in linux package in Ubuntu: Confirmed Bug description: This has now happened multiple times. When I just lock my screen (I have one external monitor attached to my laptop via HDMI) and leave my laptop alone for a while, it has somehow frozen when I get back. I'm not sure how long it will take, but something like 30-60 mins perhaps. Either one or usually both screens are just black and the machine doesn't respond to mouse or anything (haven't tried to SSH to the laptop). If I just suspend the laptop everything always goes just fine and it always wakes up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: jussili2985 F...m pulseaudio /dev/snd/controlC0: jussili2985 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 13:23:13 2019 HibernationDevice: RESUME=UUID=16017bed-4ef5-46e8-9621-733ee431d47d InstallationDate: Installed on 2018-04-17 (317 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) MachineType: LENOVO 20L5MX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5MX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET35W(1.10):bd02/12/2018:svnLENOVO:pn20L5MX:pvrThinkPadT480:rvnLENOVO:rn20L5MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5MX dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.
[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker
We are still talking to our customers whose driver is using this kernel. Please contact with Sylvain@cert to follow up the latest status. The current test result could be found here: http://people.canonical.com/~hwcert/sru-testing/current/xenial-proposed.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814647 Title: linux: 4.4.0-143.169 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial) derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 (linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Tuesday, 26. February 2019 14:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814645] Re: linux: 3.13.0-166.216 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814645 Title: linux: 3.13.0-166.216 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1814646 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Tuesday, 26. February 2019 18:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Confirmed => Triaged ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-361 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-361 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Triaged => Invalid ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Trusty) Status: New => In Progress ** No longer affects: nvidia-graphics-drivers-361 (Ubuntu) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Trusty) Status: In Progress => Invalid ** Changed in: nvidia-graphics-drivers-361 (Ubuntu Xenial) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: In Progress Status in nvidia-graphics-drivers-340 source package in Trusty: In Progress Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: In Progress Status in nvidia-graphics-drivers-304 source package in Xenial: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: In Progress Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Un
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
** Attachment added: "last part of kernel panic stack trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5242576/+files/screenshot2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Having the same problem on Windows Server 2012 (build 9200) Hyper-V with linux kernel versions 4.15.0-44 and 4.15.0-45. Last known working kernel version 4.15.0-43. Attached is a screenshot of kernel panic stack trace. ** Attachment added: "kernel panic stack trace" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5242575/+files/screenshot1.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818148] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242564/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporatio
[Kernel-packages] [Bug 1818148] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242569/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnO
[Kernel-packages] [Bug 1818148] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242573/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorpor
[Kernel-packages] [Bug 1818148] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242571/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnO
[Kernel-packages] [Bug 1818148] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242572/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracl
[Kernel-packages] [Bug 1818148] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242570/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.
[Kernel-packages] [Bug 1818148] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242568/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualB
[Kernel-packages] [Bug 1818148] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242574/+files/WifiSyslog.txt ** Summary changed: - virtualbox-guest-x11 does not work with 4.4.0-143-generic from xenial-proposed + virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) ** Description changed: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" + * unable to use shared clipboard and drag and drop fuctionalty + + Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: xenial 1850 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: - enp0s3no wireless extensions. - - lono wireless extensions. + enp0s3no wireless extensions. + + lono wireless extensions. Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: - linux-restricted-modules-4.4.0-143-generic N/A - linux-backports-modules-4.4.0-143-generic N/A - linux-firmware 1.157.21 + linux-restricted-modules-4.4.0-143-generic N/A + linux-backports-modules-4.4.0-143-generic N/A + linux-firmware 1.157.21 RfKill: - + Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH - --- + --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: xenial 1936 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: - enp0s3no wireless extensions. - - lono wireless extensions. + enp0s3no wireless extensions. + + lono wireless extensions. Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Relat
[Kernel-packages] [Bug 1818148] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242567/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnO
[Kernel-packages] [Bug 1818148] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242566/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporat
[Kernel-packages] [Bug 1818148] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1818148/+attachment/5242565/+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/1818148 Title: virtualbox-guest-x11 does not work with 4.4.0-142-generic and with 4.4.0-143-generic (from xenial-proposed) Status in linux package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have 16.04 LTS installed 2. Enable xenial-proposed repository 3. Install `virtualbox-guest-x11` package Expected results: * virtualbox-guest-x11 is working as before Actual results: * virtualbox-guest-x11 does not work, shows message after login: "VBoxClient: Failed to connect to the VirtualBox kernel service, rc=VERR_ACCESS_DENIED" * unable to use shared clipboard and drag and drop fuctionalty Note: first seen on AskUbuntu ( https://askubuntu.com/q/1122056/66509 ). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: virtualbox-guest-x11 5.1.38-dfsg-0ubuntu1.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 1 00:38:30 2019 InstallationDate: Installed on 2018-08-07 (205 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1850 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2018-01-04 (420 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 RelatedPackageVersions: linux-restricted-modules-4.4.0-143-generic N/A linux-backports-modules-4.4.0-143-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-143-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xenial 1936 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: virtualbox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=6052d85a-f0bd-4ecf-ba5e-e9e7863e8cd3 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 RelatedPackageVersions: linux-restricted-modules-4.4.0-142-generic N/A linux-backports-modules-4.4.0-142-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial Uname: Linux 4.4.0-142-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rv
