[Kernel-packages] [Bug 1812359] Re: No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on)
I've reported a bug, ** Bug watch added: Linux Kernel Bug Tracker #202487 https://bugzilla.kernel.org/show_bug.cgi?id=202487 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812359 Title: No login screen displayed on a NETBOX nT-435/535 (kernel reports an LVDS output which does not exist as connected and on) Status in linux package in Ubuntu: Triaged Bug description: On a machine with only one display (VGA), the kernel is reporting two: grep . /sys/class/drm/*/enabled /sys/class/drm/card0-LVDS-1/enabled:enabled /sys/class/drm/card0-VGA-1/enabled:enabled ls /sys/class/drm card0 card0-LVDS-1 card0-VGA-1 renderD128 version grep . /sys/class/drm/*/dpms /sys/class/drm/card0-LVDS-1/dpms:On /sys/class/drm/card0-VGA-1/dpms:On which then triggers bug 1760849 and the login screen is never visible. --- $ dpkg -s mutter Package: mutter Status: install ok installed Priority: optional Section: x11 Installed-Size: 101 Maintainer: Ubuntu Developers Architecture: amd64 Version: 3.28.3-2~ubuntu18.04.2 Provides: x-window-manager Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.53.2), libmutter-2-0 (>= 3.28.2), libx11-6, libxcomposite1 (>= 1:0.3-1), mutter-common (>= 3.28.3-2~ubuntu18.04.2), gnome-settings-daemon, gsettings-desktop-schemas (>= 3.21.4), zenity Suggests: gnome-control-center (>= 1:3.25.2), xdg-user-dirs Description: lightweight GTK+ window manager Mutter is a small window manager, using GTK+ and Clutter to do everything. . Mutter is the clutter-based evolution of Metacity, which, as the author says, is a "Boring window manager for the adult in you. Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios." . This package contains the core binaries. Original-Maintainer: Debian GNOME Maintainers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 15:02:22 2019 InstallationDate: Installed on 2019-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804874] Re: can't reconnect USB mouse/ USB mouse stops working after a while
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804874 Title: can't reconnect USB mouse/ USB mouse stops working after a while Status in linux package in Ubuntu: Expired Bug description: https://wiki.ubuntu.com/DebuggingMouseDetection#generalinfo - used this tutorial "entered following commands : LANG=C dmesg > ~/dmesg diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff " Output files are compressed and attached to this bug report. Ubuntu 18.04.1, gnome and kde installed. --- ProblemType: Bug .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-36-generic, i686: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] InstallationDate: Installed on 2014-08-26 (1550 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: ASUSTeK Computer Inc. K53E Package: xorg 1:7.7+19ubuntu7.1 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=5faedd29-769a-4472-935e-602675fb441d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: third-party-packages bionic ubuntu Uname: Linux 4.15.0-39-generic i686 UpgradeStatus: Upgraded to bionic on 2018-11-22 (0 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Oct 11 13:44:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 732 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
This also happens on my system with RX480 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (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/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814207] Re: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/q
** 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/1814207 Title: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu fails to boot and my productivity in the organization is SEVERELY AFFECTED. I AM CONSIDERING SWITCHING TO MAC/WINDOWS IF YOU DO NOT HAVE A SOLUTION. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3193 F pulseaudio fcaa18835 4098 F pulseaudio /dev/snd/controlC0: gdm3193 F pulseaudio fcaa18835 4098 F pulseaudio Date: Wed Jan 30 09:51:34 2019 DuplicateSignature: package:linux-modules-extra-4.15.0-44-generic:4.15.0-44.47 Unpacking linux-modules-extra-4.15.0-44-generic (4.15.0-44.47) ... dpkg: error processing archive /tmp/apt-dpkg-install-RhHUGr/2-linux-modules-extra-4.15.0-44-generic_4.15.0-44.47_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=e147be70-9b09-4ec1-955e-560fe8bcc144 InstallationDate: Installed on 2018-12-06 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 SourcePackage: linux Title: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 09X6YN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/10/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn09X6YN:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814207] 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/1814207 Title: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu fails to boot and my productivity in the organization is SEVERELY AFFECTED. I AM CONSIDERING SWITCHING TO MAC/WINDOWS IF YOU DO NOT HAVE A SOLUTION. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3193 F pulseaudio fcaa18835 4098 F pulseaudio /dev/snd/controlC0: gdm3193 F pulseaudio fcaa18835 4098 F pulseaudio Date: Wed Jan 30 09:51:34 2019 DuplicateSignature: package:linux-modules-extra-4.15.0-44-generic:4.15.0-44.47 Unpacking linux-modules-extra-4.15.0-44-generic (4.15.0-44.47) ... dpkg: error processing archive /tmp/apt-dpkg-install-RhHUGr/2-linux-modules-extra-4.15.0-44-generic_4.15.0-44.47_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=e147be70-9b09-4ec1-955e-560fe8bcc144 InstallationDate: Installed on 2018-12-06 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 SourcePackage: linux Title: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 09X6YN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/10/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn09X6YN:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814207] Re: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/q
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814207 Title: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu fails to boot and my productivity in the organization is SEVERELY AFFECTED. I AM CONSIDERING SWITCHING TO MAC/WINDOWS IF YOU DO NOT HAVE A SOLUTION. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm3193 F pulseaudio fcaa18835 4098 F pulseaudio /dev/snd/controlC0: gdm3193 F pulseaudio fcaa18835 4098 F pulseaudio Date: Wed Jan 30 09:51:34 2019 DuplicateSignature: package:linux-modules-extra-4.15.0-44-generic:4.15.0-44.47 Unpacking linux-modules-extra-4.15.0-44-generic (4.15.0-44.47) ... dpkg: error processing archive /tmp/apt-dpkg-install-RhHUGr/2-linux-modules-extra-4.15.0-44-generic_4.15.0-44.47_amd64.deb (--unpack): unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=e147be70-9b09-4ec1-955e-560fe8bcc144 InstallationDate: Installed on 2018-12-06 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 SourcePackage: linux Title: package linux-modules-extra-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: unable to open '/lib/modules/4.15.0-44-generic/kernel/drivers/input/keyboard/qt1070.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 09X6YN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/10/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn09X6YN:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Thanks to your comment I also realized that journald still logs the dmesg driver spam which results in bloated journald log files as well. Few more steps is required to alleviate that: 1. sudo vi /etc/systemd/journald.conf 2. Uncomment Storage=auto and change it to Storage=none 3. Uncomment ForwardToSyslog=yes 4. Save the file changes and reboot This way logs are still forwarded to syslog where i2c_hid messages are filtered by the blocklist config file but you lose the ability to monitor logs using e.g. journalctl. I would like to emphasize that this is a temporary solution which works pretty well for my purpose but might not be a good fit for others. Please try to work around this behavior on kernel driver level first before resorting to syslog/journald shenanigans. Eagerly looking forward towards a fix for Elan touchpads. -- You 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 1784152] Re: i2c_hid_get_input floods system logs
That's a good point but unfortunately unloading and reloading the module doesn't stop the messages from being produced on my system. Also, until the issue is fixed, my aim was exactly to filter unnecessary events from syslog to avoid bloated log files (kern.log and syslog) and unnecessary events since it was the biggest and probably the only real symptom for me. -- You 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 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
Confirming for both 4.15.0-44 and 4.15.0-45 on Windows Server 2012 Hyper-V. For now I've forced GRUB to boot 4.15.0-43. The guest is Ubuntu Server 18.04.1. FWIW, the VM has 2 virtual cores and dynamically-allocated memory of up to 6144 MB. I'm only able to view the boot process in Hyper-V's "Virtual Machine Connection" console, which has no scroll buffer. When boot failure occurs, I can see the last few lines of an error trace in the console, but I've been unable to capture the full trace. No information regarding the boot ends up in the system logs--i.e., journalctl doesn't recognize the failed boot attempts at all. -- You 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 1814241] Re: linux-oem: 4.15.0-1033.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** 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: 1813779 - phase: Holding before Promote to Proposed - phase-changed: Friday, 01. February 2019 13:38 UTC + phase: Promote to Proposed + phase-changed: Friday, 01. February 2019 20:36 UTC reason: - promote-to-proposed: Ongoing -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: New 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: Confirmed 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 upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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: 1813779 phase: Promote to Proposed phase-changed: Friday, 01. February 2019 20:36 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814325] 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/1814325 Title: Keyboard light fn does not works for Asus VivoBook S14 X430UA on Ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Bug description: I started using Ubuntu in my new Asus VivoBook S14 X430UA laptop. But it is very disappointing that the keyboard light cannot be controlled using the dedicated switch (fn + f7). Similarly fn + f8 also not working, which is for screen toggling. echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness command to switch on the keyboard light is working fine. Is there any solution for this issue? Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajithabhks 1491 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 01:25:22 2019 HibernationDevice: RESUME=UUID=29048cc5-d306-4844-8f70-c87fc7a20081 InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56c1 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook S14 X430UA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=911bc958-ea13-4f07-9757-ce3a56799271 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX430UA.204:bd06/06/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookS14X430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S14 X430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814325] [NEW] Keyboard light fn does not works for Asus VivoBook S14 X430UA on Ubuntu 18.04
Public bug reported: I started using Ubuntu in my new Asus VivoBook S14 X430UA laptop. But it is very disappointing that the keyboard light cannot be controlled using the dedicated switch (fn + f7). Similarly fn + f8 also not working, which is for screen toggling. echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness command to switch on the keyboard light is working fine. Is there any solution for this issue? Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ajithabhks 1491 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 01:25:22 2019 HibernationDevice: RESUME=UUID=29048cc5-d306-4844-8f70-c87fc7a20081 InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56c1 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook S14 X430UA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=911bc958-ea13-4f07-9757-ce3a56799271 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX430UA.204:bd06/06/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookS14X430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S14 X430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: I started using Ubuntu in my new Asus VivoBook S14 X430UA. But it is very disappointing that the keyboard light cannot be controlled using the dedicated switch (fn + f7). Similarly fn + f8 also not working. Now i use echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness command to switch on the keyboard light. Is there any solution for this issue? Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ajithabhks 1491 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ajithabhks 1491 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 01:25:22 2019 HibernationDevice: RESUME=UUID=29048cc5-d306-4844-8f70-c87fc7a20081 InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2b Intel Corp. - Bus 001 Device 002: ID 13d3:56c1 IMC Networks - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 13d3:56c1 IMC Networks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook S14 X430UA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=911bc958-ea13-4f07-9757-ce3a56799271 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=1 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 + 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1814308] Re: amdgpu with mst WARNING on blanking
for bionic, this looks like it requires (at least) commit 41b497421a1f07ab99814da740984f907747120b also, which is a bit more complex to backport. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814308 Title: amdgpu with mst WARNING on blanking Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Fix Released Bug description: [impact] The amdgpu driver, when configured with MST monitors (i.e. displayport "daisy-chaining"), encounters a WARNING when blanking - such as when the display(s) are put to sleep after idle timeout. [test case] on a system with a amd gpu using the amdgpu driver, that is capable and configured for displayport mst (with multiple dp daisy chained monitors), blank the screen and then wake up the screen. This will be logged: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:944 [ cut here ] WARNING: CPU: 0 PID: 2201 at /var/lib/dkms/amdgpu/18.50-690240/build/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait+0xe7/0x160 [amdgpu] Call Trace: dce110_stream_encoder_dp_blank+0x11c/0x180 [amdgpu] core_link_disable_stream+0x40/0x230 [amdgpu] ? generic_reg_update_ex+0xdb/0x130 [amdgpu] dce110_reset_hw_ctx_wrap+0xb7/0x1f0 [amdgpu] dce110_apply_ctx_to_hw+0x30/0x430 [amdgpu] ? dce110_apply_ctx_for_surface+0x206/0x260 [amdgpu] dc_commit_state+0x2ba/0x4d0 [amdgpu] amdgpu_dm_atomic_commit_tail+0x297/0xd70 [amdgpu] ? amdgpu_bo_pin_restricted+0x58/0x260 [amdgpu] ? wait_for_completion_timeout+0x1f/0x120 ? wait_for_completion_interruptible+0x1c/0x160 commit_tail+0x3d/0x60 [drm_kms_helper] drm_atomic_helper_commit+0xf6/0x100 [drm_kms_helper] drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm] drm_mode_obj_set_property_ioctl+0x14f/0x250 [drm] drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm] drm_ioctl+0x1e0/0x430 [drm] ? drm_mode_connector_set_obj_prop+0x70/0x70 [drm] ? ep_read_events_proc+0xb0/0xb0 ? ep_scan_ready_list.constprop.18+0x1e6/0x1f0 ? timerqueue_add+0x52/0x80 amdgpu_drm_ioctl+0x49/0x80 [amdgpu] do_vfs_ioctl+0x90/0x5f0 SyS_ioctl+0x74/0x80 do_syscall_64+0x74/0x140 entry_SYSCALL_64_after_hwframe+0x3d/0xa2 ---[ end trace 3ed7b77a97d60f72 ]--- [regression potential] this modifies the sequence of actions during link disabling, so any regressions would appear at that time. [other info] this is from upstream 8c9d90eebd23b6d40ddf4ce5df5ca2b932336a06 this is included in disco from bug 1812427 this is needed in bionic and cosmic the xenial kernel does not (reliably) support dp mst, so this is not needed there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
https://lists.ubuntu.com/archives/kernel-team/2019-February/098264.html -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Incomplete Status in linux-azure source package in Bionic: In Progress Status in linux source package in Cosmic: Incomplete Status in linux-azure source package in Cosmic: In Progress Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] 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 1802021 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: New => Incomplete ** Tags added: bionic -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Incomplete Status in linux-azure source package in Bionic: In Progress Status in linux source package in Cosmic: Incomplete Status in linux-azure source package in Cosmic: In Progress Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-azure (Ubuntu Bionic) ** No longer affects: linux-azure (Ubuntu Cosmic) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Cosmic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Cosmic) Importance: Undecided => Medium -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: In Progress Status in linux source package in Cosmic: New Status in linux-azure source package in Cosmic: In Progress Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock.
[Kernel-packages] [Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
** Description changed: + [impact] + + autopkgtest failure during test for linux pkg. + + ADJ_OFFSET during test causes skew, and test to fail. + + [test case] + + this only happens intermittently, but frequently on the autopkgtests. + + when it happens it looks like: + + 20:46:54 DEBUG| [stdout] WARNING: ADJ_OFFSET in progress, this will cause inaccurate results + 20:48:54 DEBUG| [stdout] Estimating clock drift: 16.881(est) 27.184(act) [FAILED] + + when it happens with a patched kernel it looks like: + + 01:04:35 DEBUG| [stdout] WARNING: ADJ_OFFSET in progress, this will cause inaccurate results + 01:06:35 DEBUG| [stdout] Estimating clock drift: 14.52(est) 13.641(act) [OK] + + [regression potential] + + since this skips the test in question, it might miss an actual + regression that the test should have caught; however, since ADJ_OFFSET + is not always in progress during the test, if a real regression happens + for this test, then it should correctly fail for test runs which have no + concurrent ADJ_OFFSET and thus don't skip the test. + + [other info] + + original description: + --- + + This issue cannot be reproduced across all of our SUTs, issue found on node secchi (3 out of 3). And sometimes on node amaura (2 out of 4) selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 03:58 seq crw-rw 1 root audio 116, 33 Jan 10 03:58 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: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFT dmi.board.vendor: Intel Corporation dmi.board.version: H48104-410 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [impact] autopkgtest failure during test for linux pkg. ADJ_OFFSET during test causes skew, and test to fail. [test case] this only happens intermittently, but frequently on the autopkgtests. when it happens it looks like: 20:46:54 DEBUG| [stdout] WARNING: ADJ_OFFSET in progress, this will cause inaccurate results 20:48:54 DEBUG| [stdout] Estimating clock drift: 16.881(est) 27.184(act) [FAILED]
[Kernel-packages] [Bug 1813664] Re: linux: 4.19.0-12.13 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** 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: derivatives: -- swm properties -- - phase: Testing - phase-changed: Tuesday, 29. January 2019 16:34 UTC + phase: Release + phase-changed: Friday, 01. February 2019 19:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813664 Title: linux: 4.19.0-12.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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: derivatives: -- swm properties -- phase: Release phase-changed: Friday, 01. February 2019 19:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1813664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813664] Re: linux: 4.19.0-12.13 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813664 Title: linux: 4.19.0-12.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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: derivatives: -- swm properties -- phase: Testing phase-changed: Tuesday, 29. January 2019 16:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1813664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
** No longer affects: linux-meta-hwe (Ubuntu) ** No longer affects: linux-meta-hwe (Ubuntu Bionic) ** No longer affects: linux-meta-hwe (Ubuntu Cosmic) -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hmmm, filtering out syslog treats only a single symptom (dmesg, etc will still have log spew) not to mention the events are still occurring resulting in wasted CPU cycles. Why not just unload and reload the module? It's much more straightforward... -- You 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 1814308] [NEW] amdgpu with mst WARNING on blanking
Public bug reported: [impact] The amdgpu driver, when configured with MST monitors (i.e. displayport "daisy-chaining"), encounters a WARNING when blanking - such as when the display(s) are put to sleep after idle timeout. [test case] on a system with a amd gpu using the amdgpu driver, that is capable and configured for displayport mst (with multiple dp daisy chained monitors), blank the screen and then wake up the screen. This will be logged: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:944 [ cut here ] WARNING: CPU: 0 PID: 2201 at /var/lib/dkms/amdgpu/18.50-690240/build/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait+0xe7/0x160 [amdgpu] Call Trace: dce110_stream_encoder_dp_blank+0x11c/0x180 [amdgpu] core_link_disable_stream+0x40/0x230 [amdgpu] ? generic_reg_update_ex+0xdb/0x130 [amdgpu] dce110_reset_hw_ctx_wrap+0xb7/0x1f0 [amdgpu] dce110_apply_ctx_to_hw+0x30/0x430 [amdgpu] ? dce110_apply_ctx_for_surface+0x206/0x260 [amdgpu] dc_commit_state+0x2ba/0x4d0 [amdgpu] amdgpu_dm_atomic_commit_tail+0x297/0xd70 [amdgpu] ? amdgpu_bo_pin_restricted+0x58/0x260 [amdgpu] ? wait_for_completion_timeout+0x1f/0x120 ? wait_for_completion_interruptible+0x1c/0x160 commit_tail+0x3d/0x60 [drm_kms_helper] drm_atomic_helper_commit+0xf6/0x100 [drm_kms_helper] drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm] drm_mode_obj_set_property_ioctl+0x14f/0x250 [drm] drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm] drm_ioctl+0x1e0/0x430 [drm] ? drm_mode_connector_set_obj_prop+0x70/0x70 [drm] ? ep_read_events_proc+0xb0/0xb0 ? ep_scan_ready_list.constprop.18+0x1e6/0x1f0 ? timerqueue_add+0x52/0x80 amdgpu_drm_ioctl+0x49/0x80 [amdgpu] do_vfs_ioctl+0x90/0x5f0 SyS_ioctl+0x74/0x80 do_syscall_64+0x74/0x140 entry_SYSCALL_64_after_hwframe+0x3d/0xa2 ---[ end trace 3ed7b77a97d60f72 ]--- [regression potential] this modifies the sequence of actions during link disabling, so any regressions would appear at that time. [other info] this is from upstream 8c9d90eebd23b6d40ddf4ce5df5ca2b932336a06 this is included in disco from bug 1812427 this is needed in bionic and cosmic the xenial kernel does not (reliably) support dp mst, so this is not needed there ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed ** Description changed: [impact] The amdgpu driver, when configured with MST monitors (i.e. displayport "daisy-chaining"), encounters a WARNING when blanking - such as when the display(s) are put to sleep after idle timeout. [test case] on a system with a amd gpu using the amdgpu driver, that is capable and configured for displayport mst (with multiple dp daisy chained monitors), blank the screen and then wake up the screen. This will be logged: - [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:944 - [ cut here ] - WARNING: CPU: 0 PID: 2201 at /var/lib/dkms/amdgpu/18.50-690240/build/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait+0xe7/0x160 [amdgpu] - Call Trace: - dce110_stream_encoder_dp_blank+0x11c/0x180 [amdgpu] - core_link_disable_stream+0x40/0x230 [amdgpu] - ? generic_reg_update_ex+0xdb/0x130 [amdgpu] - dce110_reset_hw_ctx_wrap+0xb7/0x1f0 [amdgpu] - dce110_apply_ctx_to_hw+0x30/0x430 [amdgpu] - ? dce110_apply_ctx_for_surface+0x206/0x260 [amdgpu] - dc_commit_state+0x2ba/0x4d0 [amdgpu] - amdgpu_dm_atomic_commit_tail+0x297/0xd70 [amdgpu] - ? amdgpu_bo_pin_restricted+0x58/0x260 [amdgpu] - ? wait_for_completion_timeout+0x1f/0x120 - ? wait_for_completion_interruptible+0x1c/0x160 - commit_tail+0x3d/0x60 [drm_kms_helper] - drm_atomic_helper_commit+0xf6/0x100 [drm_kms_helper] - drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm] - drm_mode_obj_set_property_ioctl+0x14f/0x250 [drm] -
[Kernel-packages] [Bug 1814308] Re: amdgpu with mst WARNING on blanking
note that i marked disco as 'fix released' but technically it's 'fix committed' - however it's being tracked for disco over in bug 1812427 as part of the normal disco stable update, so for the purposes of this bug, i think it can be considered 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/1814308 Title: amdgpu with mst WARNING on blanking Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Fix Released Bug description: [impact] The amdgpu driver, when configured with MST monitors (i.e. displayport "daisy-chaining"), encounters a WARNING when blanking - such as when the display(s) are put to sleep after idle timeout. [test case] on a system with a amd gpu using the amdgpu driver, that is capable and configured for displayport mst (with multiple dp daisy chained monitors), blank the screen and then wake up the screen. This will be logged: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:944 [ cut here ] WARNING: CPU: 0 PID: 2201 at /var/lib/dkms/amdgpu/18.50-690240/build/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait+0xe7/0x160 [amdgpu] Call Trace: dce110_stream_encoder_dp_blank+0x11c/0x180 [amdgpu] core_link_disable_stream+0x40/0x230 [amdgpu] ? generic_reg_update_ex+0xdb/0x130 [amdgpu] dce110_reset_hw_ctx_wrap+0xb7/0x1f0 [amdgpu] dce110_apply_ctx_to_hw+0x30/0x430 [amdgpu] ? dce110_apply_ctx_for_surface+0x206/0x260 [amdgpu] dc_commit_state+0x2ba/0x4d0 [amdgpu] amdgpu_dm_atomic_commit_tail+0x297/0xd70 [amdgpu] ? amdgpu_bo_pin_restricted+0x58/0x260 [amdgpu] ? wait_for_completion_timeout+0x1f/0x120 ? wait_for_completion_interruptible+0x1c/0x160 commit_tail+0x3d/0x60 [drm_kms_helper] drm_atomic_helper_commit+0xf6/0x100 [drm_kms_helper] drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm] drm_mode_obj_set_property_ioctl+0x14f/0x250 [drm] drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm] drm_ioctl+0x1e0/0x430 [drm] ? drm_mode_connector_set_obj_prop+0x70/0x70 [drm] ? ep_read_events_proc+0xb0/0xb0 ? ep_scan_ready_list.constprop.18+0x1e6/0x1f0 ? timerqueue_add+0x52/0x80 amdgpu_drm_ioctl+0x49/0x80 [amdgpu] do_vfs_ioctl+0x90/0x5f0 SyS_ioctl+0x74/0x80 do_syscall_64+0x74/0x140 entry_SYSCALL_64_after_hwframe+0x3d/0xa2 ---[ end trace 3ed7b77a97d60f72 ]--- [regression potential] this modifies the sequence of actions during link disabling, so any regressions would appear at that time. [other info] this is from upstream 8c9d90eebd23b6d40ddf4ce5df5ca2b932336a06 this is included in disco from bug 1812427 this is needed in bionic and cosmic the xenial kernel does not (reliably) support dp mst, so this is not needed there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
I can confirm that "idle=halt" makes both my Ryzen desktop and Ryzen notebook more stable than anything else I've tried. I have not experienced freezes for some days now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this
[Kernel-packages] [Bug 1690085]
(In reply to Philip Rosvall from comment #518) > I can confirm that "idle=halt" makes both my Ryzen desktop and Ryzen > notebook more stable than anything else I've tried. I have not experienced > freezes for some days now. Can you upload dmesg from the working and non-working kernels pls? Thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus:
[Kernel-packages] [Bug 1813664] Re: linux: 4.19.0-12.13 -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 backports: derivatives: -- swm properties -- phase: Testing phase-changed: Tuesday, 29. January 2019 16:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-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/1813664 Title: linux: 4.19.0-12.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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: derivatives: -- swm properties -- phase: Testing phase-changed: Tuesday, 29. January 2019 16:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1813664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Wow, lots of different devices have started shipping the same fingerprint scanner since I first raised this issue. Is there anything we can do in the community to help? Clearly there is a need for this to be included. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813179] Re: Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for VM_PFNMAP VMAs (fixed in mainline)
*** This bug is a duplicate of bug 1799237 *** https://bugs.launchpad.net/bugs/1799237 ** This bug has been marked a duplicate of bug 1799237 mprotect fails on ext4 with dax -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813179 Title: Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for VM_PFNMAP VMAs (fixed in mainline) Status in linux package in Ubuntu: Confirmed Bug description: Version: Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic Ubuntu 4.15.0-43.46-generic 4.15.18 This is a bug that has been fixed in mainline. When calling 'mprotect(..., PROT_NONE)' on a virtual memory area with VM_PFNMAP set it fails with a EACCESS (Permission denied) error even though it is a valid call. In my particular case this happens when calling mprotect(..., PROT_NONE) on a set of pages within the range of an Intel SGX enclave. The bug is fully described on the Linux kernel mailing list here: https://lkml.org/lkml/2018/8/16/697 The bug has been fixed in mainline in August, see https://github.com/torvalds/linux/commit/f19f5c49bbc3ffcc9126cc245fc1b24cc29f4a37 According to https://launchpad.net/ubuntu/+source/linux/+changelog the patch has been backported to Xenial and Cosmic, but not yet to Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
I just retried by installing headers, then reinstall kernel-generic. This time wifi works. Note that these packages won't show in Synaptic. Will show in dpkg -l|grep kernel. Use dpkg -r to remove them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814295] Re: qa-regression-testing test_ulimit_stack_small fails on ppc64el
** 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/1814295 Title: qa-regression-testing test_ulimit_stack_small fails on ppc64el Status in linux package in Ubuntu: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
** Changed in: linux (Ubuntu Bionic) Importance: Low => 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/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: This issue cannot be reproduced across all of our SUTs, issue found on node secchi (3 out of 3). And sometimes on node amaura (2 out of 4) selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 03:58 seq crw-rw 1 root audio 116, 33 Jan 10 03:58 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: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFT dmi.board.vendor: Intel Corporation dmi.board.version: H48104-410 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1811194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I have the same issue. Workarounds with driver recompilation are not really a good fit in my case since they require to set up a build system and also to enroll a MOK key for unsigned drivers to work because I have Secure Boot enabled. acpi_osi workaround disables touchpad on my system. Until the bug is fixed, here's a quicker and easier way to filter these messages on syslog level inspired by https://askubuntu.com/a/21648: 1. sudo vi /etc/rsyslog.d/01-blocklist.conf (any name after "01-" part will work) 2. Add this line: :msg,contains,"i2c_hid_get_input" ~ 3. Save the file and restart rsyslog service: sudo systemctl restart rsyslog You can make the filter more specific, i.e. filter only "incomplete report" messages instead of suppressing all output of messages containing "i2c_hid_get_input" but latter case works just fine for my purposes. Hope this helps. -- You 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 1813664] Re: linux: 4.19.0-12.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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: derivatives: -- swm properties -- phase: Testing phase-changed: Tuesday, 29. January 2019 16:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-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/1813664 Title: linux: 4.19.0-12.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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: derivatives: -- swm properties -- phase: Testing phase-changed: Tuesday, 29. January 2019 16:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1813664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793901] Re: kernel oops in bcache module
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) 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/1793901 Title: kernel oops in bcache module Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification = [Impact] Some users see panics like the following when performing fstrim on a bcached volume: [ 529.803060] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 530.183928] #PF error: [normal kernel read fault] [ 530.412392] PGD 801f42163067 P4D 801f42163067 PUD 1f42168067 PMD 0 [ 530.750887] Oops: [#1] SMP PTI [ 530.920869] CPU: 10 PID: 4167 Comm: fstrim Kdump: loaded Not tainted 5.0.0-rc1+ #3 [ 531.290204] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, BIOS P89 12/27/2015 [ 531.693137] RIP: 0010:blk_queue_split+0x148/0x620 [ 531.922205] Code: 60 38 89 55 a0 45 31 db 45 31 f6 45 31 c9 31 ff 89 4d 98 85 db 0f 84 7f 04 00 00 44 8b 6d 98 4c 89 ee 48 c1 e6 04 49 03 70 78 <8b> 46 08 44 8b 56 0c 48 8b 16 44 29 e0 39 d8 48 89 55 a8 0f 47 c3 [ 532.838634] RSP: 0018:b9b708df39b0 EFLAGS: 00010246 [ 533.093571] RAX: RBX: 00046000 RCX: [ 533.441865] RDX: 0200 RSI: RDI: [ 533.789922] RBP: b9b708df3a48 R08: 940d3b3fdd20 R09: [ 534.137512] R10: b9b708df3958 R11: R12: [ 534.485329] R13: R14: R15: 940d39212020 [ 534.833319] FS: 7efec26e3840() GS:940d1f48() knlGS: [ 535.224098] CS: 0010 DS: ES: CR0: 80050033 [ 535.504318] CR2: 0008 CR3: 001f4e256004 CR4: 001606e0 [ 535.851759] Call Trace: [ 535.970308] ? mempool_alloc_slab+0x15/0x20 [ 536.174152] ? bch_data_insert+0x42/0xd0 [bcache] [ 536.403399] blk_mq_make_request+0x97/0x4f0 [ 536.607036] generic_make_request+0x1e2/0x410 [ 536.819164] submit_bio+0x73/0x150 [ 536.980168] ? submit_bio+0x73/0x150 [ 537.149731] ? bio_associate_blkg_from_css+0x3b/0x60 [ 537.391595] ? _cond_resched+0x1a/0x50 [ 537.573774] submit_bio_wait+0x59/0x90 [ 537.756105] blkdev_issue_discard+0x80/0xd0 [ 537.959590] ext4_trim_fs+0x4a9/0x9e0 [ 538.137636] ? ext4_trim_fs+0x4a9/0x9e0 [ 538.324087] ext4_ioctl+0xea4/0x1530 [ 538.497712] ? _copy_to_user+0x2a/0x40 [ 538.679632] do_vfs_ioctl+0xa6/0x600 [ 538.853127] ? __do_sys_newfstat+0x44/0x70 [ 539.051951] ksys_ioctl+0x6d/0x80 [ 539.212785] __x64_sys_ioctl+0x1a/0x20 [ 539.394918] do_syscall_64+0x5a/0x110 [ 539.568674] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Under certain conditions, the test for whether an operation should be written back to the underlying device was incorrect. Specifically, in should_writeback(), we were hitting a case where an optimisation for partial stripe conditions was returning true and so should_writeback() was returning true early. This caused the code to go down an incorrect path and create bios that contained NULL pointers. To fix this issue, make sure that should_writeback() on a discard op never returns true. [Test Case] We have observed it on some systems where both: 1) LVM/devmapper is involved (bcache backing device is LVM volume) and 2) writeback cache is involved (bcache cache_mode is writeback) Not every machine exhibits the bug. On one machine that does exhibit the bug, we can reliably reproduce it with: # echo writeback > /sys/block/bcache0/bcache/cache_mode # mount /dev/bcache0 /test # for i in {0..10}; do file="$(mktemp /test/zero.XXX)"; dd if=/dev/zero of="$file" bs=1M count=256; sync; rm $file; done; fstrim -v /test [Regression Potential] This could affect any device where bcache is used. In mitigation, however: the patch is simple, is limited to considering discard operations. The patch has been accepted upstream [1] and the maintainer will be including it in SuSE kernels [2]. A Gentoo user validated the upstream patch independently [3]. [1]
[Kernel-packages] [Bug 1814295] 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 1814295 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/1814295 Title: qa-regression-testing test_ulimit_stack_small fails on ppc64el Status in linux package in Ubuntu: Incomplete Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change
Just removed the hold on kmod (24-1ubuntu3) and updated to kmod (24-1ubuntu3.2). The touchpad is still working. Thanks for everyone's effort on this issue. Greatly appreciate it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802135 Title: broken touchpad after i2c-i801 blacklist change Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in kmod source package in Xenial: Fix Committed Status in linux source package in Xenial: Invalid Status in kmod source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in kmod source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU: [Impact] ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801. PNP LEN0049 will use smbus by default in kernel, but i2c bus is in runtime suspend mode in old touchpad fw. Then touchpad will not work. LEN2040 on 11e 3rd can reproduce this issue by passing psmouse.synaptics_intertouch=1 These 2 pnp device should be the same one Synaptics s3203_ver5. [Fix] i2c-i801 should auto suspend when not used, no need runtime pm. [Test Case] Tested on Thinkpad 11e 3rd. Touchpad works fine. [Regression Potential] Low, upstream fix cherry-picked. 4.18 kernel patch, no need for cosmic. Original bug report: = After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 11e 2nd gen machines. We have a fleet of approximetly 1000 of them in production running ubuntu 18.04. Prior to this update the trackpads worked out of box in 18.04. We are currently working around the issue by deploying our own blacklist files. Here is a link to the SRU justification: https://bugs.launchpad.net /hwe-next/+bug/1786574 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B Power8
I see this failure in cosmic as well: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190201_014942_1b783@/log.gz ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) 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/1812796 Title: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B Power8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: This test failed on a Power8 node with Bionic kernel: [ RUN ] TRACE_syscall.ptrace_syscall_dropped seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == syscall(286) (18446744073709551615) TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 [ FAIL ] TRACE_syscall.ptrace_syscall_dropped Please find the attachment for the complete test log. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 06:09:34 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0 ProcLoadAvg: 0.13 0.34 0.23 1/1487 35882 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 2018 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' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 152) max: 3.694 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814295] [NEW] qa-regression-testing test_ulimit_stack_small fails on ppc64el
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- ** 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/1814295 Title: qa-regression-testing test_ulimit_stack_small fails on ppc64el Status in linux package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Well, I tested on my laptop with: paul@paul-NC210-NC110:~$ cat /proc/version Linux version 3.14.79-031479-generic (kernel@gloin) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #20160910530 SMP Sun Sep 11 09:41:06 UTC 2016 When I used gdebi to install the kernel .deb, in the details, there were some errors. I believe this was because I did not installed headers .deb before... I would suggest you install the headers .deb before... but it work even without the headers .deb. Also gdebi said version was already installed: I am pretty sure it was not. I lost my wifi however after rebooting with that version (I plugged Ethernet wire for writing this). And I am on Linux Mint 19.1. When I rebooted, it continue to boot with old kernel, and was not showing me the menu... even if I pressed Esc and Shift. So I edited /etc/default/grub from: GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 to: GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=10 but I think this could be needed only on Mint. after that, advanced options were showing, and I was able to select old kernel version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796791] Re: ubuntu_ftrace_smoke_test time outed on X-4.15 / B-4.15
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-signed-hwe (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796791 Title: ubuntu_ftrace_smoke_test time outed on X-4.15 / B-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-signed-hwe source package in Bionic: New Bug description: The test was killed. Compared to the test in X-4.4 (https://pastebin.ubuntu.com/p/hQDvv9qXFx/), it looks like the "tracer function can be enabled" is the one got killed. Output: PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-4.15.0-36-generic) PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-4.15.0-36-generic) PASSED (CONFIG_STACK_TRACER=y in /boot/config-4.15.0-36-generic) PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-4.15.0-36-generic) PASSED all expected /sys/kernel/debug/tracing files exist PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers) PASSED (function in /sys/kernel/debug/tracing/available_tracers) PASSED (nop in /sys/kernel/debug/tracing/available_tracers) PASSED (function can be enabled) PASSED (SyS_write traces found must be > 32, got 5575) PASSED (function_graph can be enabled) PASSED (vfs_write traces found must be > 32, got 10726) PASSED (tracer hwlat can be enabled (got 10 lines of tracing output)) PASSED (tracer blk can be enabled (got 2 lines of tracing output)) PASSED (tracer mmiotrace can be enabled (got 9 lines of tracing output)) PASSED (tracer function_graph can be enabled (got 55991 lines of tracing output)) PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output)) PASSED (tracer wakeup_rt can be enabled (got 44 lines of tracing output)) PASSED (tracer wakeup can be enabled (got 60 lines of tracing output)) TIMEOUT 1431 KILLING 1431 FAILED: aborting, timeout, took way too long to complete ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39~16.04.1 ProcVersionSignature: User Name 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Oct 9 04:59:56 2018 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1796791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
journalctl -b-1 > prevlog.txt ** Attachment added: "prevlog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+attachment/5235109/+files/prevlog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235106/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235104/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235107/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] Re: repeated segfault in svnserve
apport information ** Tags added: apport-collected uec-images ** Description changed: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Feb 1 08:02 seq + crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color + 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 090006 + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: 7.0 + dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: 7.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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 ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235100/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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
[Kernel-packages] [Bug 1814281] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235105/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235101/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235108/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235102/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1814281/+attachment/5235103/+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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 1 08:02 seq crw-rw 1 root audio 116, 33 Feb 1 08:02 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-256color 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=7efdba54-16aa-11e9-b653-00155d030d07 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: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 6893-0796-3491-2581-8383-9413-73 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012: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/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
Hi I had the same behavior and the installation of the 45 solve the issue for me and my colleague. Many thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am using a docking station for my laptop. After install the 4.15.0-44 update my external monitors goes undetected after logging in or having the laptop closed. I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2) Graphics. Going back to the 4.15.0-43 version makes it all work fine again. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonas 2407 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4 InstallationDate: Installed on 2018-10-17 (103 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004MMX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004MMX 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:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004MMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] 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 1814281 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Incomplete Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814281] [NEW] repeated segfault in svnserve
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1814281 Title: repeated segfault in svnserve Status in linux package in Ubuntu: Incomplete Bug description: Description:Ubuntu 18.04.1 LTS Release:18.04 subversion: Installed: 1.9.7-4ubuntu1 Candidate: 1.9.7-4ubuntu1 Version table: *** 1.9.7-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Multiple repeated segfaults in svnserve, e.g. Feb 01 14:13:21 svn kernel: svnserve[2631]: segfault at 7f6769b903d8 ip 7f676924b675 sp 7fff851adc40 error 4 in libsvn_subr-1.so.1.0.0[7f67691ed000+d3000] svnserve is handling 4 svn repos for local network of 40 users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
I've reverted back to before installing the Nvidia driver. Nvidia now has new drivers which I think will solve this problem, so this bug can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1814197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600
Thanks for trying the tearfree option! (ok, it don't work) By reading: https://wiki.ubuntu.com/Kernel/MainlineBuilds I discovered: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D which would allow to download prebuild .deb for old mwainline kernels. I am a bit sceptical if new versions of ubuntu would boot with so old versions. But it could help someone pinpoint the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791312 Title: ubuntu 18.04 flickering screen with Radeon X1600 Status in linux package in Ubuntu: Confirmed Bug description: my laptop: HP Compaq nx9420 my grafic card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller]) attachment: the bug-apport-file Description: I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode; -> as soon as the kernel-module radeon.ko is loaded the screen starts flickering when starting the grafic-mode the flickering continues; so the screen is unusable. when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the screen does not flicker but the resolution is limited to 1400x1050 (instead of natural 1680x1050) so I can not use this as work-around when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157) the screen is o.k. NO flickering in textmode, nice grafic, NO flickering xrandr tells: 1680x1050 60.1 so I must stay on old ubuntu 14.04.05 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
The delivery status gives: : Host or domain name not found. Name service error for name=vger.linux.org type=A: Host not found -- message/delivery-status -- Reporting-MTA: dns; mail1.protonmail.ch X-Postfix-Queue-ID: A70A02008274 X-Postfix-Sender: rfc822; t...@selwyn.cc Arrival-Date: Fri, 1 Feb 2019 10:37:45 + (UTC) Final-Recipient: rfc822; linux-...@vger.linux.org Original- Recipient: rfc822;linux-...@vger.linux.org Action: failed Status: 5.4.4 Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=vger.linux.org type=A: Host not found -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. WORKAROUND: Disable XHC1 prior to sleeping via: # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! 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 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb 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: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+subscriptions -- Mailing list: https://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 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Please please please, pretty please xD On Fri, Feb 1, 2019 at 4:41 PM risafov <1721...@bugs.launchpad.net> wrote: > Same for me: > ASUS UX370UA > Linux 18.10 > Kernel 4.20 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1721909 > > Title: > Goodix GF3208 (fingerprint reader) not being recognised by > kernel/system > > Status in Linux: > New > Status in linux package in Ubuntu: > Confirmed > > Bug description: > The Goodix GF3208 is not being recognised by the system (Dell Inspiron > 15 7577). What's worse is that it isn't even showing the manufacturer > vendor id information when doing: > > $ lsusb > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 27c6:5301 > Bus 001 Device 003: ID 8087:0a2b Intel Corp. > Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver > Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Note that the vendor id 27c6 should at least say "Shenzhen Huiding > Technology Co., Ltd." as per > > https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings > /vendor-prefixes.txt > > Will/has support been made for the Goodix GF3208 Fingerprint > reader/scanner? > > Thanks in advance, > Haz > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 > ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 > Uname: Linux 4.10.0-35-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.10 > Architecture: amd64 > CurrentDesktop: Unity > Date: Sat Oct 7 04:03:25 2017 > InstallationDate: Installed on 2017-10-01 (5 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > SourcePackage: linux-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe (Ubuntu Cosmic) Status: New => Confirmed -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-meta-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Status in linux-meta-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
** Package changed: linux-hwe (Ubuntu) => linux-meta-hwe (Ubuntu) -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-meta-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Status in linux-meta-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe (Ubuntu Bionic) Status: New => Confirmed -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux-azure package in Ubuntu: Confirmed Status in linux-meta-hwe package in Ubuntu: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux-meta-hwe source package in Bionic: Confirmed Status in linux-azure source package in Cosmic: Confirmed Status in linux-meta-hwe source package in Cosmic: Confirmed Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806380] Re: linux-buildinfo: pull out ABI information into its own package
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806380 Title: linux-buildinfo: pull out ABI information into its own package Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: We have an increasing amount of ABI information which is currently exposed via the primary binary packages. Little to none of this is relevant to the end-user and does not deserve to use up space on their system. Also the kernel developer who needs to update this data does not want to downloads 10s of Megabytes of binary packages to extract this information. Pull it all out and generate all data that would require the actual binaries at kernel build time, package all of this information into a new linux-buildinfo package for consumption. This package is not installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 11:51 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811847 Title: linux-aws: 4.4.0-1038.41 -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 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system
Same for me: ASUS UX370UA Linux 18.10 Kernel 4.20 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: The Goodix GF3208 is not being recognised by the system (Dell Inspiron 15 7577). What's worse is that it isn't even showing the manufacturer vendor id information when doing: $ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5301 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note that the vendor id 27c6 should at least say "Shenzhen Huiding Technology Co., Ltd." as per https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings /vendor-prefixes.txt Will/has support been made for the Goodix GF3208 Fingerprint reader/scanner? Thanks in advance, Haz ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 7 04:03:25 2017 InstallationDate: Installed on 2017-10-01 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 11:55 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811851 Title: linux-aws: 4.4.0-1075.85 -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 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 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: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Monday, 28. January 2019 13:01 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to 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/1811846 Title: linux: 4.4.0-142.168 -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 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: Fix Released 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811853] Re: linux-kvm: 4.4.0-1040.46 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 11:58 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811853 Title: linux-kvm: 4.4.0-1040.46 -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 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811854] Re: linux-raspi2: 4.4.0-1103.111 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1811846 - phase: Testing - phase-changed: Monday, 28. January 2019 12:59 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811854 Title: linux-raspi2: 4.4.0-1103.111 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1811846 phase: Holding before Release phase-changed: Friday, 01. February 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -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 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: Fix Released 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 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
What status should this bug be moved to? Obviously there is something fishy going on with Intel VMD being enabled, but I'm not using it so it doesn't impact me in this case. Should I get any logs to assist in figuring out why enabling VMD causes the system not boot properly? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: Incomplete Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Kernel 4.15.0-45, guest on Server 2012 R2 Hyper-V Host also affected. Last working kernel 4.15.0-43. -- You 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 1812758] Re: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU
I was able to install 18.04 without issue. It looks like the solution to disable "Intel VMD Technology" in the BIOS solved the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812758 Title: Boot failure on Dell Precision 5820 with Intel Xeon W-2123 CPU Status in linux package in Ubuntu: Incomplete Bug description: So I'm trying to install Ubuntu 16.04.5 (happens on 18.04 as well) on a Dell Precision 5820 with a GTX 1080 in it. These machines are lease refreshes. I created a UEFI image of 16.04.5, selected "Install Ubuntu" and then starts throwing a bunch of error messages stating [33.192238] nouveau :05:00.0: DRM: base-0: timeout repeating over and over again. It never gets past this. I tried the suggestions of adding "nomodeset" in grub when I'm booting. It progresses a little further but hangs at "failed to start Ubuntu Installation Service, please run journalctl to see what failed". I can't see what failed as I can't get a prompt since nothing is installed. I don't know where to go debug from here. My computer boots to a black screen, what options do I have to fix it? Graphics issues after/while installing Ubuntu 16.04/16.10 with NVIDIA graphics Ubuntu 16.04 Installation Issue Boots Into Black Screen or Freezes - Nouveau/Nvidia Driver issue 1080ti Ubuntu 16.04 installation blank screen Ubuntu 16.04 unable to boot with GTX 1080 etc. However, I tried Ubuntu 16.04.1 LTS and did NOT have the issues with the video and was successfully able to install Ubuntu 16.04.1. Unfortunately, 16.04.1 didn't support the integrated Intel i219-LM network card. I tried 16.04.2, 16.04.3, 16.04.4 and they all exhibit the same behavior as 16.04.5 with the video. Just as a test, I installed 16.04.1, installed broadcom NIC (which was successfully detected), and upgraded from 16.04.1 --> 16.04.5 with apt-get and had no video issues after reboot (I didn't install the video drivers), in addition, after it was upgraded to 16.04.5 the Intel 219-LM drivers were added and would work. I have a workaround, but it's REALLY annoying. The kicker in this is that the Dell Precision 5810 worked 100% correctly. Put the USB boot drive in, select the drive in UEFI to boot and everything works out of the box. I'm working on gathering more logs of this issue and testing different kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: 4.15.0-1033.38 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => 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 -- kernel-stable-master-bug: 1813779 - phase: Packaging - phase-changed: Friday, 01. February 2019 10:39 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 01. February 2019 13:38 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: New 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: New 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 upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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 -- kernel-stable-master-bug: 1813779 phase: Holding before Promote to Proposed phase-changed: Friday, 01. February 2019 13:38 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811860] Re: Display ports on Lenovo docking station stopped working after upgrade of linux-firmware 1.173.2 -> 1.173.3
Can you provide the output of lsmod and dmesg with the laptop attached to the dock and 1.173.3 installed? I still can't see how any of the updates between those versions are to files which would be used by your laptop. For reference, here is is the list of files added or updated between 1.173.2 and 1.173.3. The amdgpu files won't be used at all by the bionic 4.15 kernel, but you have Intel graphics hardware anyway. You do have an Intel wireless card, but not one which uses the wireless firmware which was updated. The others are not for devices which would be found in a laptop. amdgpu/vegam_ce.bin amdgpu/vegam_me.bin amdgpu/vegam_mec.bin amdgpu/vegam_mec2.bin amdgpu/vegam_pfp.bin amdgpu/vegam_rlc.bin amdgpu/vegam_sdma.bin amdgpu/vegam_sdma1.bin amdgpu/vegam_smc.bin amdgpu/vegam_uvd.bin amdgpu/vegam_vce.bin iwlwifi-9000-pu-b0-jf-b0-34.ucode iwlwifi-9260-th-b0-jf-b0-34.ucode mellanox/mlxsw_spectrum-13.1620.192.mfa2 qed/qed_init_values_zipped-8.37.2.0.bin -- 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/1811860 Title: Display ports on Lenovo docking station stopped working after upgrade of linux-firmware 1.173.2 -> 1.173.3 Status in linux-firmware package in Ubuntu: Incomplete Bug description: Lenovo Carbon X1 running on Lenovo Thinkpad Ultra Dock I have only been able to attach a single monitor to the docking station before the upgrade of linux-firmware. After todays upgrade from 1.173.2 to 1.173.3, none of the outputs work anymore. The Ultra Dock has two DP, an HDMI, and a VGA output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 16:31:39 2019 Dependencies: InstallationDate: Installed on 2018-12-03 (42 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1811860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Here is some information relevant to this thread. An update from Ubuntu that 12c_i801 *re*-blacklists just arrived on my Mint PC. I had it blacklisted on my system anyway. A while ago, it was blacklisted by default, but then a Debian update removed it from the blacklist. Now, for Ubuntu and derivatives at least, it is back on the blacklist. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 )
[Kernel-packages] [Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
I believe this is fixed (worked around, by skipping the test when ADJ_OFFSET is detected) by upstream commit 1416270f4a1ae83ea84156ceba19a66a8f88be1f: commit 1416270f4a1ae83ea84156ceba19a66a8f88be1f Author: John Stultz Date: Tue May 29 19:12:18 2018 -0700 selftest: timers: Tweak raw_skew to SKIP when ADJ_OFFSET/other clock adjustments are in progress This commit is included upstream in v4.19, already included in cosmic (and disco) via bug 1794597, already included in xenial via bug 1798587. Does not appear that it's in bionic yet. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: This issue cannot be reproduced across all of our SUTs, issue found on node secchi (3 out of 3). And sometimes on node amaura (2 out of 4) selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 03:58 seq crw-rw 1 root audio 116, 33 Jan 10 03:58 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: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFT dmi.board.vendor: Intel Corporation dmi.board.version: H48104-410 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1811194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
frederick@graphMetrix-1:~$ sudo apt --fix-broken install [sudo] password for frederick: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libsdl-ttf2.0-0 linux-headers-4.18.0-10 linux-headers-4.18.0-10-generic linux-image-4.18.0-10-generic linux-modules-4.18.0-10-generic linux-modules-extra-4.18.0-10-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libelf1:i386 libwayland-client0:i386 libwayland-server0:i386 The following NEW packages will be installed: libelf1:i386 libwayland-client0:i386 libwayland-server0:i386 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. 7 not fully installed or removed. Need to get 0 B/104 kB of archives. After this operation, 367 kB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 276791 files and directories currently installed.) Preparing to unpack .../libelf1_0.170-0.5.0ubuntu1_i386.deb ... Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 Preparing to unpack .../libwayland-client0_1.16.0-1ubuntu1.1_i386.deb ... Unpacking libwayland-client0:i386 (1.16.0-1ubuntu1.1) ... dpkg: error processing archive /var/cache/apt/archives/libwayland-client0_1.16.0-1ubuntu1.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libwayland-client0/changelog.Debian.gz', which is different from other instances of package libwayland-client0:i386 Preparing to unpack .../libwayland-server0_1.16.0-1ubuntu1.1_i386.deb ... Unpacking libwayland-server0:i386 (1.16.0-1ubuntu1.1) ... dpkg: error processing archive /var/cache/apt/archives/libwayland-server0_1.16.0-1ubuntu1.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Errors were encountered while processing: /var/cache/apt/archives/libelf1_0.170-0.5.0ubuntu1_i386.deb /var/cache/apt/archives/libwayland-client0_1.16.0-1ubuntu1.1_i386.deb /var/cache/apt/archives/libwayland-server0_1.16.0-1ubuntu1.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
** Changed in: linux (Ubuntu Xenial) 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/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 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed
Selwyn: "! I could not send the email though, the email address "linux- u...@vger.linux.org" seems invalid." If you post the email source of the message sent, and what you may have received in a response, then this may be assessed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812561 Title: [MacBookPro11,5] wakes up and suspends in a loop while closed Status in linux package in Ubuntu: Triaged Bug description: Similar bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/ The first time suspending works great but after that suspending causes the laptop to wake up regardless of the method used to suspend. WORKAROUND: Disable XHC1 prior to sleeping via: # echo XHC1 > /proc/acpi/wakeup Sidenote: thanks to penalvch for explaining how to report this! 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 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: siilwyn1852 F pulseaudio /dev/snd/controlC1: siilwyn1852 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 13:40:14 2019 InstallationDate: Installed on 2019-01-19 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb 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: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Monday, 28. January 2019 11:49 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 12:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to 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/1811856 Title: linux: 3.13.0-165.215 -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: Fix Released 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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Holding before Release phase-changed: Friday, 01. February 2019 12:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804604] Re: SRU: Fix thinkpad 11e 3rd boot hang
** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1804604 Title: SRU: Fix thinkpad 11e 3rd boot hang Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] ThinkPad 11e 3rd boot hang in systemd loading. [Fix] When boot case acpi_lpss_resume() get called without a corresponding acpi_lpss_suspend() having been called. Thus force setting the flag during boot. [Test Case] Tested on Thinkpad 11e 3rd. Booting successfully. [Regression Potential] Low, upstream fix cherry-picked. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812229] Re: Bionic update: upstream stable patchset 2019-01-17
** 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/1812229 Title: Bionic update: upstream stable patchset 2019-01-17 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-01-17 (ported from v4.14.58 and v4.17.10) from git://git.kernel.org/ scsi: sd_zbc: Fix variable type and bogus comment KVM/Eventfd: Avoid crash when assign and deassign specific eventfd in parallel. x86/apm: Don't access __preempt_count with zeroed fs x86/events/intel/ds: Fix bts_interrupt_threshold alignment x86/MCE: Remove min interval polling limitation fat: fix memory allocation failure handling of match_strdup() ALSA: hda/realtek - Add Panasonic CF-SZ6 headset jack quirk ARCv2: [plat-hsdk]: Save accl reg pair by default ARC: Fix CONFIG_SWAP ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs ARC: mm: allow mprotect to make stack mappings executable mm: memcg: fix use after free in mem_cgroup_iter() mm/huge_memory.c: fix data loss when splitting a file pmd cpufreq: intel_pstate: Register when ACPI PCCH is present vfio/pci: Fix potential Spectre v1 stop_machine: Disable preemption when waking two stopper threads drm/i915: Fix hotplug irq ack on i965/g4x drm/nouveau: Use drm_connector_list_iter_* for iterating connectors drm/nouveau: Avoid looping through fake MST connectors gen_stats: Fix netlink stats dumping in the presence of padding ipv4: Return EINVAL when ping_group_range sysctl doesn't map to user ns ipv6: fix useless rol32 call on hash ipv6: ila: select CONFIG_DST_CACHE lib/rhashtable: consider param->min_size when setting initial table size net: diag: Don't double-free TCP_NEW_SYN_RECV sockets in tcp_abort net: Don't copy pfmemalloc flag in __copy_skb_header() skbuff: Unconditionally copy pfmemalloc in __skb_clone() net/ipv4: Set oif in fib_compute_spec_dst net: phy: fix flag masking in __set_phy_supported ptp: fix missing break in switch qmi_wwan: add support for Quectel EG91 tg3: Add higher cpu clock for 5762. hv_netvsc: Fix napi reschedule while receive completion is busy net/mlx4_en: Don't reuse RX page when XDP is set net: systemport: Fix CRC forwarding check for SYSTEMPORT Lite ipv6: make DAD fail with enhanced DAD when nonce length differs net: usb: asix: replace mii_nway_restart in resume path alpha: fix osf_wait4() breakage cxl_getfile(): fix double-iput() on alloc_file() failures powerpc/powernv: Fix save/restore of SPRG3 on entry/exit from stop (idle) xhci: Fix perceived dead host due to runtime suspend race with event handler KVM: irqfd: fix race between EPOLLHUP and irq_bypass_register_consumer x86/kvmclock: set pvti_cpu0_va after enabling kvmclock ALSA: hda/realtek - Yet another Clevo P950 quirk entry drm/amdgpu: Reserve VM root shared fence slot for command submission (v3) rhashtable: add restart routine in rhashtable_free_and_destroy() sch_fq_codel: zero q->flows_cnt when fq_codel_init fails sctp: introduce sctp_dst_mtu sctp: fix the issue that pathmtu may be set lower than MINSEGMENT net: aquantia: vlan unicast address list correct handling drm_mode_create_lease_ioctl(): fix open-coded filp_clone_open() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811857] Re: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1811856 - phase: Testing - phase-changed: Monday, 28. January 2019 11:58 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 12:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Ongoing -- testing in progress + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1811857 Title: linux-lts-trusty: 3.13.0-165.215~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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: 1811856 phase: Holding before Release phase-changed: Friday, 01. February 2019 12:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811877] Re: Bionic update: upstream stable patchset 2019-01-15
** 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/1811877 Title: Bionic update: upstream stable patchset 2019-01-15 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-01-15 (ported from v4.14.57 and v4.17.9) from git://git.kernel.org/ compiler-gcc.h: Add __attribute__((gnu_inline)) to all inline declarations x86/asm: Add _ASM_ARG* constants for argument registers to x86/paravirt: Make native_save_fl() extern inline Btrfs: fix duplicate extents after fsync of file with prealloc extents cpufreq / CPPC: Set platform specific transition_delay_us PCI: exynos: Fix a potential init_clk_resources NULL pointer dereference alx: take rtnl before calling __alx_open from resume atm: Preserve value of skb->truesize when accounting to vcc atm: zatm: Fix potential Spectre v1 ipv6: sr: fix passing wrong flags to crypto_alloc_shash() ipvlan: fix IFLA_MTU ignored on NEWLINK ixgbe: split XDP_TX tail and XDP_REDIRECT map flushing net: dccp: avoid crash in ccid3_hc_rx_send_feedback() net: dccp: switch rx_tstamp_last_feedback to monotonic clock net: fix use-after-free in GRO with ESP net: macb: Fix ptp time adjustment for large negative delta net/mlx5e: Avoid dealing with vport representors if not being e-switch manager net/mlx5: E-Switch, Avoid setup attempt if not being e-switch manager net/mlx5: Fix command interface race in polling mode net/mlx5: Fix incorrect raw command length parsing net/mlx5: Fix required capability for manipulating MPFS net/mlx5: Fix wrong size allocation for QoS ETC TC regitster net: mvneta: fix the Rx desc DMA address in the Rx path net/packet: fix use-after-free net_sched: blackhole: tell upper qdisc about dropped packets net: sungem: fix rx checksum support net/tcp: Fix socket lookups with SO_BINDTODEVICE qede: Adverstise software timestamp caps when PHC is not available. qed: Fix setting of incorrect eswitch mode. qed: Fix use of incorrect size in memcpy call. qed: Limit msix vectors in kdump kernel to the minimum required count. r8152: napi hangup fix after disconnect stmmac: fix DMA channel hang in half-duplex mode strparser: Remove early eaten to fix full tcp receive buffer stall tcp: fix Fast Open key endianness tcp: prevent bogus FRTO undos with non-SACK flows vhost_net: validate sock before trying to put its fd VSOCK: fix loopback on big-endian systems net: cxgb3_main: fix potential Spectre v1 rtlwifi: Fix kernel Oops "Fw download fail!!" rtlwifi: rtl8821ae: fix firmware is not ready to run net: lan78xx: Fix race in tx pending skb size calculation crypto: af_alg - Initialize sg_num_bytes in error code path mtd: rawnand: denali_dt: set clk_x_rate to 200 MHz unconditionally PCI: hv: Disable/enable IRQs rather than BH in hv_compose_msi_msg() netfilter: ebtables: reject non-bridge targets reiserfs: fix buffer overflow with long warning messages KEYS: DNS: fix parsing multiple options tls: Stricter error checking in zerocopy sendmsg path autofs: fix slab out of bounds read in getname_kernel() nsh: set mac len based on inner packet bdi: Fix another oops in wb_workfn() rds: avoid unenecessary cong_update in loop transport net/nfc: Avoid stalls when nfc_alloc_send_skb() returned NULL. string: drop __must_check from strscpy() and restore strscpy() usages in cgroup nfsd: COPY and CLONE operations require the saved filehandle to be set net/sched: act_ife: fix recursive lock and idr leak net/sched: act_ife: preserve the action control in case of error hinic: reset irq affinity before freeing irq nfp: flower: fix mpls ether type detection net: macb: initialize bp->queues[0].bp for at91rm9200 enic: do not overwrite error code virtio_net: fix memory leak in XDP_REDIRECT netfilter: ipv6: nf_defrag: drop skb dst before queueing ipvs: initialize tbl->entries after allocation ipvs: initialize tbl->entries in ip_vs_lblc_init_svc() bpf: enforce correct alignment for instructions bpf, arm32: fix to use bpf_jit_binary_lock_ro api To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811877/+subscriptions --
[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
Meetoo. My Lenovo Thinkpad T470s (20HF0047IX) with '45' kernel works as expected. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: I am using a docking station for my laptop. After install the 4.15.0-44 update my external monitors goes undetected after logging in or having the laptop closed. I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2) Graphics. Going back to the 4.15.0-43 version makes it all work fine again. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonas 2407 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4 InstallationDate: Installed on 2018-10-17 (103 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20HF004MMX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-44-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF004MMX 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:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF004MMX dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: 3.13.0-165.215 -proposed tracker
Verification tests completed successfully. ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811856 Title: linux: 3.13.0-165.215 -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: Fix Released 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 1811857 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 28. January 2019 11:49 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/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
there is no separate modesetting driver anymore, it's folded in the server that said, the bug is most likely in the kernel ** Package changed: xserver-xorg-video-modesetting (Ubuntu) => xorg- server (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
I'm also getting a Segmentation Fault with Gimp: ``` GNU Image Manipulation Program version 2.10.6 git-describe: GIMP_2_10_4-278-g0a8173ffde C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-4ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-4ubuntu1) using GEGL version 0.4.8 (compiled against version 0.4.8) using GLib version 2.58.1 (compiled against version 2.57.2) using GdkPixbuf version 2.38.0 (compiled against version 2.36.12) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.0 (compiled against version 2.13.0) using Cairo version 1.15.12 (compiled against version 1.15.12) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 9501 - Thread 9501 # [New LWP 9502] [New LWP 9503] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (fd=12, buf=0x7ffd389644d0, nbytes=256) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target IdFrame * 1Thread 0x7fc9dee16e00 (LWP 9501) "gimp-2.10" __libc_read (fd=12, buf=0x7ffd389644d0, nbytes=256) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7fc9dcf25700 (LWP 9502) "gmain" 0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28f8feb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 3Thread 0x7fc9dc724700 (LWP 9503) "gdbus" 0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28fa9890, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 Thread 3 (Thread 0x7fc9dc724700 (LWP 9503)): #0 0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28fa9890, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 resultvar = 18446744073709551100 sc_cancel_oldtype = 0 sc_ret = #1 0x7fc9e1f73e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7fc9e1f741d2 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #3 0x7fc9e28ef7b6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #4 0x7fc9e1f9c135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #5 0x7fc9e1d80164 in start_thread (arg=) at pthread_create.c:486 ret = pd = now = unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140504963630848, 8221769982414159155, 140725552829518, 140725552829519, 140725552829648, 140504963627264, -8247743653170905805, -8247679106546401997}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = #6 0x7fc9e1ca8def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 No locals. Thread 2 (Thread 0x7fc9dcf25700 (LWP 9502)): #0 0x7fc9e1c9c6d9 in __GI___poll (fds=0x558c28f8feb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 resultvar = 18446744073709551100 sc_cancel_oldtype = 0 sc_ret = #1 0x7fc9e1f73e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7fc9e1f73f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #3 0x7fc9e1f73fb1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #4 0x7fc9e1f9c135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #5 0x7fc9e1d80164 in start_thread (arg=) at pthread_create.c:486 ret = pd = now = unwind_buf =
[Kernel-packages] [Bug 1814197] Re: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is
frederick@graphMetrix-1:~$ sudo dpkg -P libnvidia-gl-390:i386 libgl1-mesa-dri:i386 [sudo] password for frederick: dpkg: dependency problems prevent removal of libnvidia-gl-390:i386: libnvidia-ifr1-390:i386 depends on libnvidia-gl-390. dpkg: error processing package libnvidia-gl-390:i386 (--purge): dependency problems - not removing dpkg: dependency problems prevent removal of libgl1-mesa-dri:i386: libglx-mesa0:i386 depends on libgl1-mesa-dri. dpkg: error processing package libgl1-mesa-dri:i386 (--purge): dependency problems - not removing Errors were encountered while processing: libnvidia-gl-390:i386 libgl1-mesa-dri:i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1814197 Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc /libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Bug description: Trying to install nvidia-driver-390 on Dell XPS 15 6570 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libwayland-server0 1.16.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompositorRunning: None Date: Thu Jan 31 18:32:20 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-14-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-14-generic, x86_64: installed DuplicateSignature: package:libwayland-server0:1.16.0-1ubuntu1.1 Unpacking libelf1:i386 (0.170-0.5.0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dAqKVk/12-libelf1_0.170-0.5.0ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libelf1/changelog.Debian.gz', which is different from other instances of package libelf1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-01-31 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: wayland Title: package libwayland-server0 1.16.0-1ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwayland-server0/changelog.Debian.gz', which is different from other instances of package libwayland-server0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-0ubuntu0.18.10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1811647] Re: Xenial update: 4.4.170 upstream stable release
** Changed in: linux (Ubuntu Xenial) 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/1811647 Title: Xenial update: 4.4.170 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 4.4.170 upstream stable release from git://git.kernel.org/ Linux 4.4.170 power: supply: olpc_battery: correct the temperature units intel_th: msu: Fix an off-by-one in attribute store genwqe: Fix size check ceph: don't update importing cap's mseq when handing cap export iommu/vt-d: Handle domain agaw being less than iommu agaw 9p/net: put a lower bound on msize b43: Fix error in cordic routine gfs2: Fix loop in gfs2_rbm_find dlm: memory leaks on error path in dlm_user_request() dlm: lost put_lkb on error path in receive_convert() and receive_unlock() dlm: possible memory leak on error path in create_lkb() dlm: fixed memory leaks after failed ls_remove_names allocation ALSA: usb-audio: Fix an out-of-bound read in create_composite_quirks ALSA: usb-audio: Avoid access before bLength check in build_audio_procunit() ALSA: cs46xx: Potential NULL dereference in probe crypto: x86/chacha20 - avoid sleeping with preemption disabled sunrpc: use SVC_NET() in svcauth_gss_* functions sunrpc: fix cache_head leak due to queued request mm, devm_memremap_pages: kill mapping "System RAM" support mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL hwpoison, memory_hotplug: allow hwpoisoned pages to be offlined fork: record start_time late scsi: zfcp: fix posting too many status read buffers leading to adapter shutdown Input: omap-keypad - fix idle configuration to not block SoC idle states scsi: bnx2fc: Fix NULL dereference in error handling xfrm: Fix bucket count reported to userspace checkstack.pl: fix for aarch64 Input: restore EV_ABS ABS_RESERVED ARM: imx: update the cpu power up timing setting on i.mx6sx powerpc: Fix COFF zImage booting on old powermacs spi: bcm2835: Unbreak the build of esoteric configs x86/kvm/vmx: do not use vm-exit instruction length for fast MMIO when running nested CIFS: Fix error mapping for SMB2_LOCK command which caused OFD lock problem MIPS: Align kernel load address to 64KB MIPS: Ensure pmd_present() returns false after pmd_mknotpresent() media: vivid: free bitmap_cap when updating std/timings/etc. cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader. spi: bcm2835: Avoid finishing transfer prematurely in IRQ mode spi: bcm2835: Fix book-keeping of DMA termination spi: bcm2835: Fix race on DMA termination ext4: force inode writes when nfsd calls commit_metadata() ext4: fix EXT4_IOC_GROUP_ADD ioctl ext4: missing unlock/put_page() in ext4_try_to_write_inline_data() ext4: fix possible use after free in ext4_quota_enable perf pmu: Suppress potential format-truncation warning KVM: x86: Use jmp to invoke kvm_spurious_fault() from .fixup Input: elan_i2c - add ACPI ID for touchpad in ASUS Aspire F5-573G usb: r8a66597: Fix a possible concurrency use-after-free bug in r8a66597_endpoint_disable() USB: serial: option: add Fibocom NL678 series USB: serial: pl2303: add ids for Hewlett-Packard HP POS pole displays ALSA: hda/tegra: clear pending irq handlers ALSA: hda: add mute LED support for HP EliteBook 840 G4 ALSA: emux: Fix potential Spectre v1 vulnerabilities ALSA: pcm: Fix potential Spectre v1 vulnerability ALSA: emu10k1: Fix potential Spectre v1 vulnerabilities ALSA: rme9652: Fix potential Spectre v1 vulnerability sock: Make sock->sk_stamp thread-safe gro_cell: add napi_disable in gro_cells_destroy xen/netfront: tolerate frags with no data VSOCK: Send reset control packet when socket is partially bound vhost: make sure used idx is seen before log in vhost_add_used_n() sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event packet: validate address length if non-zero packet: validate address length netrom: fix locking in nr_find_socket() isdn: fix kernel-infoleak in capi_unlocked_ioctl ipv6: explicitly initialize udp6_addr in udp_sock_create6() ieee802154: lowpan_header_create check must check daddr ibmveth: fix DMA unmap error in ibmveth_xmit_start error path ax25: fix a use-after-free in ax25_fillin_cb() ipv4: Fix potential
[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -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: 1813779 - phase: Testing - phase-changed: Monday, 28. January 2019 11:51 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + promote-to-security: Holding -- cycle not ready to release + promote-to-updates: Holding -- cycle not ready to release -- 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/1811423 Title: linux-azure: 4.15.0-1037.39 -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: 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: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811252] Re: Xenial update: 4.4.169 upstream stable release
** Changed in: linux (Ubuntu Xenial) 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/1811252 Title: Xenial update: 4.4.169 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 4.4.169 upstream stable release from git://git.kernel.org/ Linux 4.4.169 ALSA: isa/wavefront: prevent some out of bound writes rtc: snvs: Add timeouts to avoid kernel lockups rtc: snvs: add a missing write sync i2c: scmi: Fix probe error on devices with an empty SMB0001 ACPI device node i2c: axxia: properly handle master timeout cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs) ARM: 8814/1: mm: improve/fix ARM v7_dma_inv_range() unaligned address handling mv88e6060: disable hardware level MAC learning libata: whitelist all SAMSUNG MZ7KM* solid-state disks Input: omap-keypad - fix keyboard debounce configuration clk: mmp: Off by one in mmp_clk_add() ide: pmac: add of_node_put() drivers/tty: add missing of_node_put() drivers/sbus/char: add of_node_put() sbus: char: add of_node_put() SUNRPC: Fix a potential race in xprt_connect() bonding: fix 802.3ad state sent to partner when unbinding slave ARC: io.h: Implement reads{x}()/writes{x}() drm/msm: Grab a vblank reference when waiting for commit_done x86/earlyprintk/efi: Fix infinite loop on some screen widths scsi: vmw_pscsi: Rearrange code to avoid multiple calls to free_irq during unload scsi: libiscsi: Fix NULL pointer dereference in iscsi_eh_session_reset mac80211_hwsim: fix module init error paths for netlink mac80211: Fix condition validating WMM IE mac80211: don't WARN on bad WMM parameters from buggy APs f2fs: fix a panic caused by NULL flush_cmd_control Revert "drm/rockchip: Allow driver to be shutdown on reboot/kexec" powerpc/msi: Fix NULL pointer access in teardown code tracing: Fix memory leak of instance function hash filters tracing: Fix memory leak in set_trigger_filter() MMC: OMAP: fix broken MMC on OMAP15XX/OMAP5910/OMAP310 aio: fix spectre gadget in lookup_ioctx pinctrl: sunxi: a83t: Fix IRQ offset typo for PH11 powerpc/boot: Fix random libfdt related build errors timer/debug: Change /proc/timer_list from 0444 to 0400 lib/interval_tree_test.c: allow users to limit scope of endpoint lib/rbtree-test: lower default params lib/rbtree_test.c: make input module parameters lib/interval_tree_test.c: allow full tree search lib/interval_tree_test.c: make test options module parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811080] Re: Xenial update: 4.4.168 upstream stable release
** Changed in: linux (Ubuntu Xenial) 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/1811080 Title: Xenial update: 4.4.168 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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: 4.4.168 upstream stable release from git://git.kernel.org/ Linux 4.4.168 selftests: Move networking/timestamping from Documentation rocker: fix rocker_tlv_put_* functions for KASAN staging: speakup: Replace strncpy with memcpy matroxfb: fix size of memcpy media: dvb-frontends: fix i2c access helpers for KASAN proc: do not access cmdline nor environ from file-backed areas proc: don't use FOLL_FORCE for reading cmdline and environment mm: replace access_remote_vm() write parameter with gup_flags mm: replace __access_remote_vm() write parameter with gup_flags mm: replace get_user_pages() write/force parameters with gup_flags mm: replace get_vaddr_frames() write/force parameters with gup_flags mm: replace get_user_pages_locked() write/force parameters with gup_flags mm: replace get_user_pages_unlocked() write/force parameters with gup_flags mm/nommu.c: Switch __get_user_pages_unlocked() to use __get_user_pages() mm: remove write/force parameters from __get_user_pages_unlocked() mm: remove write/force parameters from __get_user_pages_locked() sr: pass down correctly sized SCSI sense buffer swiotlb: clean up reporting hugetlbfs: fix bug in pgoff overflow checking hugetlbfs: check for pgoff value overflow hugetlbfs: fix offset overflow in hugetlbfs mmap mm/hugetlb.c: don't call region_abort if region_chg fails posix-timers: Sanitize overrun handling wil6210: missing length check in wmi_set_ie bpf: Prevent memory disambiguation attack bpf/verifier: Pass instruction index to check_mem_access() and check_xadd() bpf/verifier: Add spi variable to check_stack_write() bpf: support 8-byte metafield access KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL KVM: SVM: Move spec control call after restore of GS x86/KVM/VMX: Expose SPEC_CTRL Bit(2) to the guest x86/bugs, KVM: Support the combination of guest and host IBRS x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end} x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec x86: fix SMAP in 32-bit environments x86: reorganize SMAP handling in user space accesses KVM/x86: Remove indirect MSR op calls from SPEC_CTRL KVM/SVM: Allow direct access to MSR_IA32_SPEC_CTRL KVM/VMX: Allow direct access to MSR_IA32_SPEC_CTRL KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES KVM/x86: Add IBPB support KVM: VMX: make MSR bitmaps per-VCPU KVM: VMX: introduce alloc_loaded_vmcs KVM: nVMX: Eliminate vmcs02 pool KVM: nVMX: mark vmcs12 pages dirty on L2 exit KVM: nVMX: fix msr bitmaps to prevent L2 from accessing L0 x2APIC ALSA: pcm: remove SNDRV_PCM_IOCTL1_INFO internal command pstore: Convert console write to use ->write_buf ocfs2: fix potential use after free debugobjects: avoid recursive calls with kmemleak hfsplus: do not free node before using hfs: do not free node before using ocfs2: fix deadlock caused by ocfs2_defrag_extent() fscache, cachefiles: remove redundant variable 'cache' fscache: fix race between enablement and dropping of object xen: xlate_mmu: add missing header to fix 'W=1' warning drm/ast: fixed reading monitor EDID not stable issue net: hisilicon: remove unexpected free_netdev ixgbe: recognize 1000BaseLX SFP modules as 1Gbps net: thunderx: fix NULL pointer dereference in nic_remove KVM: x86: fix empty-body warnings USB: omap_udc: fix USB gadget functionality on Palm Tungsten E USB: omap_udc: fix omap_udc_start() on 15xx machines USB: omap_udc: fix crashes on probe error and module removal USB: omap_udc: use devm_request_irq() bpf: fix check of allowed specifiers in bpf_trace_printk exportfs: do not read dentry after free ASoC: omap-dmic: Add pm_qos handling to avoid overruns with CPU_IDLE ASoC: omap-mcpdm: Add pm_qos handling to avoid under/overruns with CPU_IDLE Btrfs: send, fix infinite loop due to directory
[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
$ apt-cache policy linux-image-generic upower gnome-control-center gnome-shell linux-image-generic: Installed: 4.18.0.14.15 Candidate: 4.18.0.14.15 Version table: *** 4.18.0.14.15 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.18.0.13.14 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 4.18.0.10.11 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages upower: Installed: 0.99.8-2ubuntu0.2 Candidate: 0.99.8-2ubuntu0.2 Version table: *** 0.99.8-2ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.99.8-2ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 0.99.8-2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages gnome-control-center: Installed: 1:3.30.2-1ubuntu0.18.10.2 Candidate: 1:3.30.2-1ubuntu0.18.10.2 Version table: *** 1:3.30.2-1ubuntu0.18.10.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:3.30.2-1ubuntu0.18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 1:3.30.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages gnome-shell: Installed: 3.30.2-0ubuntu1.18.10.1 Candidate: 3.30.2-0ubuntu1.18.10.1 Version table: *** 3.30.2-0ubuntu1.18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.30.1-2ubuntu1.18.10.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 3.30.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Triaged Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1811432] Re: linux-gcp: 4.15.0-1027.28~16.04.1 -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: 1813779 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:46 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1811432 Title: linux-gcp: 4.15.0-1027.28~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: 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: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -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: 1811406 - phase: Release Holding - phase-changed: Monday, 28. January 2019 12:28 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811417 Title: linux-kvm: 4.18.0-1007.7 -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 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -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: 1811406 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:38 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -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 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1811406 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814241] Re: linux-oem: 4.15.0-1033.38 -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 -- kernel-stable-master-bug: 1813779 phase: Packaging phase-changed: Friday, 01. February 2019 10:39 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1814241 Title: linux-oem: 4.15.0-1033.38 -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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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 upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: 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 -- kernel-stable-master-bug: 1813779 phase: Packaging phase-changed: Friday, 01. February 2019 10:39 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811420] Re: linux-raspi2: 4.15.0-1031.33 -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: 1813779 - phase: Release Holding - phase-changed: Friday, 01. February 2019 10:36 UTC + phase: Holding before Release + phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1811420 Title: linux-raspi2: 4.15.0-1031.33 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released 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: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: 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: 1813779 phase: Holding before Release phase-changed: Friday, 01. February 2019 11:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- cycle not ready to release promote-to-updates: Holding -- cycle not ready to release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp