[Kernel-packages] [Bug 1751497] Re: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2
[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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1751497 Title: Bionic daily build - nouveau: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Status in linux package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Won't Fix Bug description: [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 Hello, from time to time I find this annoying messages in dmesg in various Ubuntu versions (I believe since 16.04 or 16.10 up until now, including Bionic Beaver daily build). From time to time, the gdm3 crashes. The current HW/SW setup will be described below. I cannot replicate the situation, but it happens. See the excerpt from dmesg output below. [9.386558] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [9.399079] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12 [9.399134] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13 [9.399208] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [9.399274] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.312741] r8169 :03:00.0 enp3s0: link up [ 12.312748] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready [ 13.439863] rfkill: input handler disabled [ 15.125569] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 136.559610] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 [ 136.559618] nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 [ 136.559619] nouveau :01:00.0: msvld: unable to load firmware data [ 136.559622] nouveau :01:00.0: msvld: init failed, -19 [ 1376.746130] lp: driver loaded but no devices found [ 1376.756790] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 1381.398605] do_IRQ: 1.37 No irq handler for vector rr HW setup: Asrock Extreme 6 Z97 Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz, 3563 MHz nVidia GK107 [GeForce GT 640] SW setup: Linux bionic 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@bionic:~# lsmod | grep nouveau nouveau 1716224 5 i2c_algo_bit 16384 1 nouveau ttm 106496 1 nouveau drm_kms_helper167936 1 nouveau mxm_wmi16384 1 nouveau drm 401408 8 nouveau,ttm,drm_kms_helper wmi24576 2 mxm_wmi,nouveau video 40960 1 nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748638] Re: System freezing
[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/1748638 Title: System freezing Status in linux package in Ubuntu: Expired Bug description: System completely freezes quite frequently, not responding to any action nor key combination. I have to long press the power button to reboot the system or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ondra 1891 F pulseaudio CurrentDesktop: GNOME Date: Sat Feb 10 15:56:56 2018 HibernationDevice: RESUME=UUID=5e25406d-d414-dbcf-2b96-f5139433cc2b InstallationDate: Installed on 2017-12-26 (45 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20F1001YMC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=871d7486-df77-4e2e-a7d2-47938e1b1773 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2018-01-12 (28 days ago) dmi.bios.date: 11/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1HET70W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F1001YMC dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1HET70W(1.34):bd11/13/2017:svnLENOVO:pn20F1001YMC:pvrThinkPadL560:rvnLENOVO:rn20F1001YMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L560 dmi.product.name: 20F1001YMC dmi.product.version: ThinkPad L560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy
** Changed in: libinput (Ubuntu) Status: Incomplete => 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/1746740 Title: XPS13 L322X Bionic (daily dev) touchpad laggy Status in libinput: Fix Released Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Also, all function keys work as expected, even F6 (keyboard 3-states backlight), but OSD picture for this last feature randomly auto- triggers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1876 F pulseaudio CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 14:05:22 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577140] Re: Wifi Ralink R3290 disabled by default in ubuntu 16.04
@Kai-Heng Feng - I have no idea about kernel bisectionBut yes there is a good news..this bug is finally fixed(don't know if further updates will cause WIFI issue again) in 18.04 release :) WIFI worked without any configuration. Please check with latest Ubuntu 18.04 Release in live mode if it works in live mode then surely it will work after installation as well. and let everyone know about this fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577140 Title: Wifi Ralink R3290 disabled by default in ubuntu 16.04 Status in linux package in Ubuntu: Confirmed Bug description: I have my personal laptop and it contains PCI Ralink r3290 wifi adaptor with bluetooth and when i have installed the fresh version of Ubuntu 16.04x64 it doesn’t work at all on boot up. The wifi is disabled by default and the it doesn’t activates even by pressing the key and when i go the network settings airplane mode is also enabled and when i try to disable airplane mode it switches back on. I dont know whats going wrong. Earlier my wifi works on ubuntu 15.04. I have tried almost every solution and none works in the latest LTS release. Please help I am unable to use internet in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shankey1536 F pulseaudio /dev/snd/controlC1: shankey1536 F pulseaudio CurrentDesktop: Unity Date: Sun May 1 17:02:12 2016 HibernationDevice: RESUME=UUID=9fdda691-a6ae-4494-99e3-b76fde1f33a6 InstallationDate: Installed on 2016-04-24 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard Compaq 15 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=609ae58a-a43f-4f7b-9a61-e21d3caf457a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.39 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.52 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.39:bd05/26/2015:svnHewlett-Packard:pnCompaq15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Compaq 15 Notebook PC dmi.product.version: 0991100600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy
Opened a bug here: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1767559 Haven't done an SRU request before, so we'll see how it goes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746740 Title: XPS13 L322X Bionic (daily dev) touchpad laggy Status in libinput: Fix Released Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Also, all function keys work as expected, even F6 (keyboard 3-states backlight), but OSD picture for this last feature randomly auto- triggers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1876 F pulseaudio CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 14:05:22 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1746740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU
I reinstalled 16.04 and reinstalled nvidia drivers, and I was able to properly disengage the discrete gpu under prime profiles. This issue seems to only affect 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767531] [NEW] Bluetooth built-in adapter not found anymore
Public bug reported: After system update (sudo apt upgrade), the bluetooth built-in adapter is not found anymore! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-122-generic 4.4.0-122.146 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eleno 2067 F pulseaudio CurrentDesktop: KDE Date: Fri Apr 27 20:58:43 2018 HibernationDevice: RESUME=UUID=306b4640-477f-449d-9f64-419bf92d85a8 InstallationDate: Installed on 2016-09-26 (578 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5557 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed root=UUID=abbfc562-261f-43ce-baf6-1ac574bf81dc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-122-generic N/A linux-backports-modules-4.4.0-122-generic N/A linux-firmware 1.157.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0WT51R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd04/25/2016:svnDellInc.:pnInspiron5557:pvr:rvnDellInc.:rn0WT51R:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5557 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767531 Title: Bluetooth built-in adapter not found anymore Status in linux package in Ubuntu: New Bug description: After system update (sudo apt upgrade), the bluetooth built-in adapter is not found anymore! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-122-generic 4.4.0-122.146 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eleno 2067 F pulseaudio CurrentDesktop: KDE Date: Fri Apr 27 20:58:43 2018 HibernationDevice: RESUME=UUID=306b4640-477f-449d-9f64-419bf92d85a8 InstallationDate: Installed on 2016-09-26 (578 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5557 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed root=UUID=abbfc562-261f-43ce-baf6-1ac574bf81dc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-122-generic N/A linux-backports-modules-4.4.0-122-generic N/A linux-firmware 1.157.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0WT51R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd04/25/2016:svnDellInc.:pnInspiron5557:pvr:rvnDellInc.:rn0WT51R:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5557 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU
I seem to be having an issue like this as well. I did a fresh install of 18.04 yesterday, and while the nvidia x server application states that the discrete gpu is turned off, i have a hardware light on my laptop that shows it to still be active, even though the nvidia x server settings show the integrated gpu to be in use, and there's additional fan noise and heat that typically accompanies the discrete gpu when the internal is selected. intel i-5 2410M nvidia 550M according to nvidia, the 390 drivers are appropriate compatable with my hardware. 16.04 did not share this error, and when the discrete gpu was deactivated to run the integrated gpu, it would truly switch off. Is there another fix for this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
This regression does not affect Xenial, so the fix is redundant. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Color dithering not working correctly because the graphics driver assumes the panel support 8bpc, but the panel only supports 6bpc. [Test] User reports the issue start appearing from v4.8-rc2. The issue is fixed with the patch. [Fix] Add a quirk to tell DRM that this panel only supports 6bpc. [Regression Potential] Low. This fix matches a very specific panel. === Original Bug Report === - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA 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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LA 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/1749420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
With a different install of Bionic in my notebook, the problem is happening too. This appears on dmesg: [ 95.285073] [ cut here ] [ 95.285109] NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out [ 95.285165] WARNING: CPU: 3 PID: 0 at /build/linux-5s7Xkn/linux-4.15.0/net/sched/sch_generic.c:323 dev_watchdog+0x221/0x230 [ 95.285170] Modules linked in: rfcomm ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 bridge stp llc devlink ebtable_filter ebtables bnep binfmt_misc nls_iso8859_1 arc4 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core media snd_compress rtsx_usb_ms memstick btusb btrtl btbcm btintel bluetooth ecdh_generic snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm ip6t_REJECT snd_seq_midi nf_reject_ipv6 snd_seq_midi_event xt_hl ip6t_rt ath10k_pci ath10k_core ath mac80211 cfg80211 snd_rawmidi snd_seq snd_seq_device snd_timer nf_conntrack_ipv6 [ 95.285324] nf_defrag_ipv6 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc input_leds aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf joydev serio_raw intel_wmi_thunderbolt snd mei_me mei shpchp soundcore intel_pch_thermal ipt_REJECT nf_reject_ipv4 ideapad_laptop sparse_keymap xt_limit tpm_crb mac_hid acpi_pad xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack sch_fq_codel libcrc32c iptable_filter parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb uas usb_storage i915 i2c_algo_bit drm_kms_helper [ 95.285473] syscopyarea sysfillrect sysimgblt fb_sys_fops ahci r8169 psmouse drm libahci mii wmi video [ 95.285511] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.15.0-20-generic #21-Ubuntu [ 95.285515] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN43WW 07/10/2017 [ 95.285531] RIP: 0010:dev_watchdog+0x221/0x230 [ 95.285542] RSP: 0018:9158f3583e58 EFLAGS: 00010286 [ 95.285549] RAX: RBX: RCX: [ 95.285554] RDX: 00040400 RSI: 00f6 RDI: 0300 [ 95.285558] RBP: 9158f3583e88 R08: 0001 R09: 042a [ 95.285562] R10: 9158f3583ee0 R11: R12: 0001 [ 95.285567] R13: 9158e971e000 R14: 9158e971e478 R15: 9158de262480 [ 95.285574] FS: () GS:9158f358() knlGS: [ 95.285579] CS: 0010 DS: ES: CR0: 80050033 [ 95.285584] CR2: 7f4ee6b2a000 CR3: 0001ff80a001 CR4: 003606e0 [ 95.285590] DR0: DR1: DR2: [ 95.285594] DR3: DR6: fffe0ff0 DR7: 0400 [ 95.285596] Call Trace: [ 95.285602] [ 95.285619] ? dev_deactivate_queue.constprop.33+0x60/0x60 [ 95.285632] call_timer_fn+0x30/0x130 [ 95.285645] run_timer_softirq+0x3fb/0x450 [ 95.285658] ? ktime_get+0x43/0xa0 [ 95.285669] ? lapic_next_deadline+0x26/0x30 [ 95.285682] __do_softirq+0xdf/0x2b2 [ 95.285693] irq_exit+0xb6/0xc0 [ 95.285703] smp_apic_timer_interrupt+0x71/0x130 [ 95.285712] apic_timer_interrupt+0x84/0x90 [ 95.285716] [ 95.285727] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [ 95.285732] RSP: 0018:a98200d13e68 EFLAGS: 0246 ORIG_RAX: ff11 [ 95.285739] RAX: 9158f35a2880 RBX: 00162f6decee RCX: 001f [ 95.285751] RDX: 00162f6decee RSI: fffd0406ee17 RDI: [ 95.285756] RBP: a98200d13ea8 R08: 0682 R09: 0f7b [ 95.285760] R10: a98200d13e38 R11: 00b5 R12: 9158f35ac900 [ 95.285763] R13: 0006 R14: bab71e78 R15: [ 95.285776] ? cpuidle_enter_state+0x97/0x2f0 [ 95.285785] cpuidle_enter+0x17/0x20 [ 95.285799] call_cpuidle+0x23/0x40 [ 95.285807] do_idle+0x18c/0x1f0 [ 95.285817] cpu_startup_entry+0x73/0x80 [ 95.285826] start_secondary+0x1a6/0x200 [ 95.285836] secondary_startup_64+0xa5/0xb0 [ 95.285842] Code: 38 00 49 63 4e e8 eb 92 4c 89 ef c6 05 e7 55 d9 00 01 e8 23 38 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 40 6d 79 ba e8 ef 03 81 ff <0f> 0b eb c0 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 [ 95.286003] ---[ end trace cd56da1f7e4ebcb2 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card
[Kernel-packages] [Bug 1767356] Re: Long boot time (approx 5 minuntes!), long shutdown
Hello dino99! My system worked fine until only a few days ago whilst I was still using 17.10... My system then started to fail to boot (blank screen) after a recent update/upgrade command: sudo apt update sudo apt upgrade The following kernels starting causing a problem: 4.13.0-38 4.13.0-39 I had to log in with Recovery Mode and was relieved to be able to upgrade distro to Bionic Beaver! At least I can log in now, but it takes about 5 minutes! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767356 Title: Long boot time (approx 5 minuntes!), long shutdown Status in linux package in Ubuntu: Confirmed Bug description: SCENARIO: I have just upgraded to 18.04 from 17.10 PROBLEM PACKAGE (?): linux-modules-4.15.0-20-generic REPORT FROM 'dmesg' shows this typical error: [ 899.040146] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out [ 909.280160] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out BASIC DETAILS: 'flip_done' timed out does not sound good to me! Is this the reason for the extremely long boot time observed? Approximate boot time is 5 minutes! Long delays on shutdown also. The new system works great once it is up and running! My laptop is 10 years old (Comapaq Presario A900), but it has worked well with Ubuntu over the years and I was hoping that the 18.04 would have a *faster* boot time, so I was excited to install the new system. Alas, it now suffers from excessively long boot time which I am convinced is due to a timeout error. But I do not have enough knowledge to know exactly what exactly is 'timing out'? (Integrated graphics card possibly?) Graphics card details: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03) Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-modules-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deeks 1979 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 13:22:59 2018 Dependencies: HibernationDevice: RESUME=UUID=0d34d409-a1d3-4f01-84d4-68614f421c15 InstallationDate: Installed on 2017-01-09 (472 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard Compaq Presario A900 Notebook PC ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c6b4332f-0c76-444c-9302-4fbab6c58497 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) dmi.bios.date: 01/24/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30ED dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.1F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.24:bd01/24/2008:svnHewlett-Packard:pnCompaqPresarioA900NotebookPC:pvrF.24:rvnHewlett-Packard:rn30ED:rvr83.1F:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: Compaq Presario A900 Notebook PC dmi.product.version: F.24 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759723] Comment bridged from LTC Bugzilla
--- Comment From jos...@br.ibm.com 2018-04-27 16:54 EDT--- I was told to write a small documentation describing what happens without the two patches mentioned in my comment #20. We basically lose the ability to hotplug/unplug CPUs into virtual machines. Considering that blk-mq enqueue tasks using 'for_each_present_cpu()' (that iterates over CPUs in systems that don't support CPU hotplug - refer to those patches for technical details) we can also have problems if tasks are scheduled to CPUs present but not online. So I suggest to *not* run VMs with extra CPUs to be hotplugged later, like: -smp 8,sockets=1,cores=2,threads=8,maxcpus=16 or 16 If we want a guest with 16 CPUs it's better to define it beforehand, for instance: -smp 16,sockets=1,cores=2,threads=8 or 16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task
[Kernel-packages] [Bug 1765025] Re: test_regression_testsuite in ubuntu_qrt_apparmor failed with 4.15 kvm
Hi Po-Hsu, The apparmor mount test is failing because while testing mounting, it is attempting to mount with the option MS_MANDLOCK and bionic's linux-kvm kernel has CONFIG_MANDATORY_FILE_LOCKING disabled, causing the operation to fail even when apparmor is not involved. Given that upstream seems to believe the code enabled by CONFIG_MANDATORY_FILE_LOCKING is little-used and buggy, I do not believe that disabling this option in the linux-kvm kernel is a bug (though it is a difference in behavior with the generic kernel). The correct fix here is probably to have the apparmor test use a different mount option. Thanks. ** Changed in: qa-regression-testing Status: New => Confirmed ** Changed in: qa-regression-testing Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Invalid ** Also affects: apparmor Importance: Undecided Status: New ** Summary changed: - test_regression_testsuite in ubuntu_qrt_apparmor failed with 4.15 kvm + apparmor mount regression test fails when CONFIG_MANDATORY_FILE_LOCKING is disabled ** Changed in: apparmor Status: New => Triaged ** Changed in: qa-regression-testing Assignee: (unassigned) => Steve Beattie (sbeattie) ** Changed in: apparmor Assignee: (unassigned) => Steve Beattie (sbeattie) -- 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/1765025 Title: apparmor mount regression test fails when CONFIG_MANDATORY_FILE_LOCKING is disabled Status in AppArmor: Triaged Status in QA Regression Testing: Triaged Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: New Bug description: Like bug 1760672, the test_regression_testsuite in ubuntu_qrt_apparmor failed with 4.15.0-1004-kvm But the error message is a little bit different. The "mount" test failed in this case. FAIL: test_regression_testsuite (__main__.ApparmorTestsuites) Run kernel regression tests -- Traceback (most recent call last): File "./test-apparmor.py", line 1716, in test_regression_testsuite self.assertEqual(expected, rc, result + report) AssertionError: Got exit code 2, expected 0 running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) (ioperm) (iopl) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3444 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3481 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3769 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3803 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3842 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibvqbxov/source/bionic/apparmor-2.12/tests/regression/apparmor/prologue.inc: line 264: 3881 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test
[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference
Also maybe related as I am running TLP: https://www.spinics.net/lists /linux-usb/msg167941.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763594 Title: xhci hangs; reset results in NULL pointer dereference Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Now and then, my xhci bus will hang, resulting in these kinds of messages in dmesg: [252220.002102] xhci_hcd :00:14.0: xHC is not running. [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up [252220.133794] usb 1-2: USB disconnect, device number 2 [252220.135042] usb 1-7: USB disconnect, device number 3 [252220.137455] usb 1-8: USB disconnect, device number 4 [252220.243317] usb 1-9: USB disconnect, device number 5 Usually, I can fix this bij resetting the bus by calling a script reset-xhci: for xhci in /sys/bus/pci/drivers/?hci_hcd ; do cd $xhci echo Resetting devices from $xhci... for i in :??:??.? ; do echo -n "$i" > unbind echo -n "$i" > bind done done But doing this today resulted in a kernel bug: [252243.401814] xhci_hcd :00:14.0: remove, state 4 [252243.401887] usb usb2: USB disconnect, device number 1 [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered [252243.470378] xhci_hcd :00:14.0: remove, state 4 [252243.470383] usb usb1: USB disconnect, device number 1 [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19 [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed. [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered [252243.475938] [ cut here ] [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device [252243.475951] WARNING: CPU: 2 PID: 1787 at /build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 pci_disable_device+0x9c/0xc0 [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE nf_nat_masquerade_ipv4 [252243.475984] xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq btrtl [252243.476023] iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 [252243.476067] raid0 multipath linear dm_mirror dm_region_hash dm_log usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ptp aesni_intel psmouse drm pps_core rtsx_pci aes_x86_64 ahci crypto_simd glue_helper libahci wmi cryptd video [252243.476089] CPU: 2 PID: 1787 Comm: reset-xhci Tainted: G U W
[Kernel-packages] [Bug 1765977] Re: HiSilicon HNS NIC names are truncated in /proc/interrupts
ubuntu@d05-1:~$ cat /proc/version Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018 ubuntu@d05-1:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //' enahisic2i0-tx0 enahisic2i0-tx1 enahisic2i0-tx2 enahisic2i0-tx3 enahisic2i0-tx4 enahisic2i0-tx5 enahisic2i0-tx6 enahisic2i0-tx7 enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx10 enahisic2i0-tx11 enahisic2i0-tx12 enahisic2i0-tx13 enahisic2i0-tx14 enahisic2i0-tx15 ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765977 Title: HiSilicon HNS NIC names are truncated in /proc/interrupts Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] HiSilicon HNS NIC names are truncated in /proc/interrupts, making it difficult for an admin to associate activity among adapters in the system. [Test Case] $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //' Without the fix: enahisic2i0-tx0 enahisic2i0-tx1 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 With the fix: enahisic2i0-tx0 enahisic2i0-tx1 enahisic2i0-tx2 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx10 enahisic2i0-tx11 enahisic2i0-tx12 enahisic2i0-tx13 enahisic2i0-tx14 enahisic2i0-tx15 [Regression Risk] Upstream patch, restricted to a single driver for a system we can directly test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Tried it on my machine, it does not solve the touchpad problems on Chuwi Lapbook air, i think it has a different touchpad than what that fix solves. lavjamanxd@sargeras:~/Downloads$ uname --all Linux sargeras 4.15.0-20-generic #21~lp1728244 SMP Fri Apr 27 13:19:49 CST 2018 x86_64 x86_64 x86_64 GNU/Linux :c -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766614] Re: linux-aws: 4.4.0-1056.65 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- 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/1766614 Title: linux-aws: 4.4.0-1056.65 -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: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762812] Re: /dev/ipmi enumeration flaky on Cavium Sabre nodes
ubuntu@hotdog:~$ cat /proc/version Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018 ubuntu@hotdog:~$ sudo ipmitool lan print Set in Progress : Set Complete Auth Type Support : MD5 Auth Type Enable: Callback : MD5 : User : MD5 : Operator : MD5 : Admin: MD5 : OEM : MD5 IP Address Source : DHCP Address IP Address : 0.0.0.0 Subnet Mask : 0.0.0.0 MAC Address : SNMP Community String : AMI IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10 BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Gratituous ARP Intrvl : 0.0 seconds Default Gateway IP : 0.0.0.0 Default Gateway MAC : 00:00:00:00:00:00 Backup Gateway IP : 0.0.0.0 Backup Gateway MAC : 00:00:00:00:00:00 802.1q VLAN ID : Disabled 802.1q VLAN Priority: 0 RMCP+ Cipher Suites : 0,1,2,3,6,7,8,11,12,15,16,17 Cipher Suite Priv Max : caaaXXX : X=Cipher Suite Unused : c=CALLBACK : u=USER : o=OPERATOR : a=ADMIN : O=OEM Bad Password Threshold : 0 Invalid password disable: no Attempt Count Reset Int.: 0 ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762812 Title: /dev/ipmi enumeration flaky on Cavium Sabre nodes Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). *** Note that systems need to be running firmware 6.2 or greater *** [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767504] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: chaotic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767504 Title: Dell XPS 15 9560 - No brightness control Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have the problem that I cannot control the screen brightness on my XPS 15 9560 notebook. /sys/class/backlight is empty. I'm running latest Dell BIOS firmware 1.9.4. I tried all kinds of kernel parameters, such as acpi_osi and acpi_backlight, but without any effect. I'm running with Intel graphics card in UEFI mode. kern.log attached. root@eris:/etc/default# uname -a Linux eris 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767490] Re: Add d-i support for Huawei NICs
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: 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/1767490 Title: Add d-i support for Huawei NICs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The hinic driver isn't included in the installer, so it isn't possible to use Huawei NICs for network installs. [Test Case] Boot d-i on a system with a Huawei PCIe card. Proceed to the network configuration screen, and see if that NIC is displayed. [Regression Risk] Including a new driver is a common practice that should have minimal regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767504] Re: Dell XPS 15 9560 - No brightness control
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767504/+attachment/5128913/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767504 Title: Dell XPS 15 9560 - No brightness control Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have the problem that I cannot control the screen brightness on my XPS 15 9560 notebook. /sys/class/backlight is empty. I'm running latest Dell BIOS firmware 1.9.4. I tried all kinds of kernel parameters, such as acpi_osi and acpi_backlight, but without any effect. I'm running with Intel graphics card in UEFI mode. kern.log attached. root@eris:/etc/default# uname -a Linux eris 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760712] Re: perf vendor events arm64: Enable JSON events for ThunderX2 B0
ubuntu@hotdog:~$ sudo perf list | grep thunderx2 thunderx2 imp def: ubuntu@hotdog:~$ cat /proc/version Linux version 4.13.0-40-generic (buildd@bos02-arm64-005) (gcc version 7.2.0 (Ubuntu/Linaro 7.2.0-8ubuntu3.2)) #45-Ubuntu SMP Wed Apr 25 08:03:23 UTC 2018 ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760712 Title: perf vendor events arm64: Enable JSON events for ThunderX2 B0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] We enabled ThunderX2 vendor events in LP: #1747523. That was sufficient for A2 silicon, but needs an update to recognize B0 silicon. [Test Case] Successful output on ThunderX2 B0 silicon: $ sudo perf list | grep thunderx2 thunderx2 imp def: $ [Regression Risk] This teaches existing code about a new SoC, which should mitigate regressions for all other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767504] [NEW] Dell XPS 15 9560 - No brightness control
Public bug reported: Hello, I have the problem that I cannot control the screen brightness on my XPS 15 9560 notebook. /sys/class/backlight is empty. I'm running latest Dell BIOS firmware 1.9.4. I tried all kinds of kernel parameters, such as acpi_osi and acpi_backlight, but without any effect. I'm running with Intel graphics card in UEFI mode. kern.log attached. root@eris:/etc/default# uname -a Linux eris 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: chaotic ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1767504/+attachment/5128912/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767504 Title: Dell XPS 15 9560 - No brightness control Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have the problem that I cannot control the screen brightness on my XPS 15 9560 notebook. /sys/class/backlight is empty. I'm running latest Dell BIOS firmware 1.9.4. I tried all kinds of kernel parameters, such as acpi_osi and acpi_backlight, but without any effect. I'm running with Intel graphics card in UEFI mode. kern.log attached. root@eris:/etc/default# uname -a Linux eris 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765850] Re: arm64: fix CONFIG_DEBUG_WX address reporting
ubuntu@hotdog:~$ dmesg | grep W+X [ 35.653992] arm64/mm: Found insecure W+X mapping at address 00ac9000/0x00ac9000 [ 36.046414] Checked W+X mappings: FAILED, 12 W+X pages found, 0 non-UXN pages found Yep, that's in the userspace mapping. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765850 Title: arm64: fix CONFIG_DEBUG_WX address reporting Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: [Impact] The warnings emitted by the kernel when CONFIG_DEBUG_WX is enabled will show an incorrect address, nullifying the value of this config option. [Test Case] Boot; if a "arm64/mm: Found insecure W+X mapping at address" message appears, confirm it's not in the userspace mapping. [Regression Risk] This is arm64-only code, so regressions would be restricted to arm64. This change is currently present in bionic without any noticed regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766599] Re: linux-oem: 4.13.0-1025.28 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- 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/1766599 Title: linux-oem: 4.13.0-1025.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766605] Re: linux-aws: 4.4.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- 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/1766605 Title: linux-aws: 4.4.0-1018.18 -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: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767443] 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 1767443 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/1767443 Title: regular hard lockup on bionic kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767443] Re: regular hard lockup on bionic kernel
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Tags removed: kernel-da-key ** Tags added: kernel-key ** Also affects: linux (Ubuntu Bionic) Importance: High 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/1767443 Title: regular hard lockup on bionic kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767490] [NEW] Add d-i support for Huawei NICs
Public bug reported: [Impact] The hinic driver isn't included in the installer, so it isn't possible to use Huawei NICs for network installs. [Test Case] Boot d-i on a system with a Huawei PCIe card. Proceed to the network configuration screen, and see if that NIC is displayed. [Regression Risk] Including a new driver is a common practice that should have minimal regression risk. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: 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/1767490 Title: Add d-i support for Huawei NICs Status in linux package in Ubuntu: In Progress Bug description: [Impact] The hinic driver isn't included in the installer, so it isn't possible to use Huawei NICs for network installs. [Test Case] Boot d-i on a system with a Huawei PCIe card. Proceed to the network configuration screen, and see if that NIC is displayed. [Regression Risk] Including a new driver is a common practice that should have minimal regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766610] Re: linux-kvm: 4.4.0-1022.27 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1766610 Title: linux-kvm: 4.4.0-1022.27 -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: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766614] Re: linux-aws: 4.4.0-1056.65 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1766614 Title: linux-aws: 4.4.0-1056.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766592] Re: linux: 4.13.0-40.45 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766592 Title: linux: 4.13.0-40.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: 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 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem) derivatives: bug 1766593 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755627] Re: ibrs/ibpb fixes result in excessive kernel logging
Verified fixed in all affected -proposed kernels: trusty 3.13.0-146.195 xenial 4.4.0-123.147 artful 4.13.0-40.45 ** Tags removed: verification-needed-artful verification-needed-trusty verification-needed-xenial ** Tags added: verification-done-artful verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755627 Title: ibrs/ibpb fixes result in excessive kernel logging 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 Artful: Fix Committed Bug description: Since at least kernel 4.4.0-116, every invocation of `sysctl -a` results in kernel logs similar to the following: % sysctl -a &>/dev/null; dmesg -T | tail -8 [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0 The output varies with the number of CPUs. After digging a bit, it turns out this is triggered upon every read of `kernel.ibrs_dump`: % for i in {1..3}; do sysctl kernel.ibrs_dump; dmesg -T | tail -8; echo; sleep 1; done kernel.ibrs_dump = 0 [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0 kernel.ibrs_dump = 0 [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0 kernel.ibrs_dump = 0 [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0 Those tests were against an EC2 instance running Ubuntu 4.4.0-116.140-generic 4.4.98 per /proc/version_signature Normally this would not be the biggest concern but we have tooling that gathers instance info on a schedule, including sysctl output, thus resulting in the kernel ring buffer being full of nothing but said output in most cases and hindering live troubleshooting as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766596] Re: linux-gcp: 4.13.0-1014.18 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1766596 Title: linux-gcp: 4.13.0-1014.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766599] Re: linux-oem: 4.13.0-1025.28 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1766599 Title: linux-oem: 4.13.0-1025.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766605] Re: linux-aws: 4.4.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** 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: 1766604 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 27. April 2018 19:34 UTC ** 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: 1766604 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 27. April 2018 19:34 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1766605 Title: linux-aws: 4.4.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766604] Re: linux: 4.4.0-123.147 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766604 Title: linux: 4.4.0-123.147 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1766605 (linux-aws), bug 1766607 (linux-lts-xenial) derivatives: bug 1766608 (linux-snapdragon), bug 1766610 (linux-kvm), bug 1766611 (linux-euclid), bug 1766612 (linux-raspi2), bug 1766614 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766605] Re: linux-aws: 4.4.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1766605 Title: linux-aws: 4.4.0-1018.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767443] Re: regular hard lockup on bionic kernel
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767443 Title: regular hard lockup on bionic kernel Status in linux package in Ubuntu: New Bug description: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766610] Re: linux-kvm: 4.4.0-1022.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-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: 1766604 phase: Uploaded + kernel-stable-phase-changed:Friday, 27. April 2018 19:16 UTC + kernel-stable-phase:Promoted to 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: 1766604 - phase: Uploaded - kernel-stable-phase-changed:Friday, 27. April 2018 19:16 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1766610 Title: linux-kvm: 4.4.0-1022.27 -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: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766614] Re: linux-aws: 4.4.0-1056.65 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** 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: 1766604 phase: Uploaded + kernel-stable-phase-changed:Friday, 27. April 2018 19:19 UTC + kernel-stable-phase:Promoted to 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: 1766604 - phase: Uploaded - kernel-stable-phase-changed:Friday, 27. April 2018 19:19 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1766614 Title: linux-aws: 4.4.0-1056.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766604 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749420] Re: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749420 Title: [regression] Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Color dithering not working correctly because the graphics driver assumes the panel support 8bpc, but the panel only supports 6bpc. [Test] User reports the issue start appearing from v4.8-rc2. The issue is fixed with the patch. [Fix] Add a quirk to tell DRM that this panel only supports 6bpc. [Regression Potential] Low. This fix matches a very specific panel. === Original Bug Report === - Ubuntu 18.04 (with updates as of 14 Feb 2018). - Laptop: Asus Zenbook UX303 - CPU: Intel i5 4210U - Graphics: Intel HD 4400 Problem description: Colour artefacts and banding in all apps. Graphics, photos and videos display as though the colour range is improperly configured. See this photo of a 1080p video taken with a camera (poor quality, but illustrates the issue): https://ubuntucommunity.s3-us- east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg Look at the sky’s light colours. They display with smooth gradients on Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the video with a smaller range of white colours. This is the most apparent with either very dark or very light colours. Even on window titlebars the banding is visible (displayed as lines with different shades of grey/black). Compared with a PrtSc shot of the same image: https://i.imgur.com/VkOSCaQ.png The artefacts are not present on PrtSc shots that are taken on Ubuntu 18.04 but viewed on a different system (16.04 and Windows). Installing a previous kernel version fixes the issue completely. I used UKUU Update Utility to install kernel 4.4 (the same that I use in Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on 18.04 everything displayed smoothly. So this indicates that the system might be using a sub-optimal colour depth with the newer kernel? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: boot/vmlinuz-4.13.0-32-generic] ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ystein 1344 F pulseaudio /dev/snd/controlC1: ystein 1344 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Feb 14 11:25:43 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1 InstallationDate: Installed on 2018-02-12 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LA 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
[Kernel-packages] [Bug 1766573] Re: linux < 4.11: unable to use netfilter logging from non-init namespaces
SRU Request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-April/092032.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766573 Title: linux < 4.11: unable to use netfilter logging from non-init namespaces Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: Was disabled by the following patch (linux 3.10): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69b34fb996b2 netfilter: xt_LOG: add net namespace support for xt_LOG And fixed in linux 4.11: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2851940ffee3 netfilter: allow logging from non-init namespaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763454] Re: bpf_map_lookup_elem: BUG: unable to handle kernel paging request
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763454 Title: bpf_map_lookup_elem: BUG: unable to handle kernel paging request Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: Some unfortunate timing between the fix for CVE-2017-17862 being backported and some updates from upstream stable resulted in us not having some hunks from the CVE patch. This is causing oopses (see below). Fix: Add in the missing hunks from the CVE patch. Test case: See test results in comment #4. Regression potential: This just updates the code to match the upstream patch, which has been upstream for months, so regression potential should be low. --- Hey, we are currently debugging an issue with Scope [1] where the initialization of the used tcptracer-bpf [2] leads to a kernel oops at the first call of `bpf_map_lookup_elem`. The OS is Ubuntu Xenial with kernel version `Ubuntu 4.4.0-119.143-generic 4.4.114`. `4.4.0-116.140` does not show the problem. Example: ``` [ 58.763045] BUG: unable to handle kernel paging request at 3c0c41a8 [ 58.846450] IP: [] bpf_map_lookup_elem+0x6/0x20 [ 58.909436] PGD 80003be04067 PUD 3bea1067 PMD 0 [ 58.914876] Oops: [#1] SMP [ 58.915581] Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc overlay vboxsf isofs ppdev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vboxguest input_leds serio_raw parport_pc parport video ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mptspi aesni_intel scsi_transport_spi mptscsih aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd mptbase psmouse e1000 [ 59.678145] CPU: 1 PID: 1810 Comm: scope Not tainted 4.4.0-119-generic #143-Ubuntu [ 59.790501] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 59.846405] task: 88003ae23800 ti: 880022c84000 task.ti: 880022c84000 [ 60.000524] RIP: 0010:[] [] bpf_map_lookup_elem+0x6/0x20 [ 60.178029] RSP: 0018:880022c87960 EFLAGS: 00010082 [ 60.257957] RAX: 8117cd70 RBX: c922f090 RCX: [ 60.350704] RDX: RSI: 880022c87ba8 RDI: 3c0c4180 [ 60.449182] RBP: 880022c87be8 R08: R09: 0800 [ 60.547638] R10: 88003ae23800 R11: 88003ca12e10 R12: [ 60.570757] R13: 88003c601200 R14: 88003fd10020 R15: 880022c87d10 [ 60.678811] FS: 7f95ba372700() GS:88003fd0() knlGS: [ 60.778636] CS: 0010 DS: ES: CR0: 80050033 [ 60.866380] CR2: 3c0c41a8 CR3: 3aeae000 CR4: 00060670 [ 60.963736] DR0: DR1: DR2: [ 61.069195] DR3: DR6: fffe0ff0 DR7: 0400 [ 61.187006] Stack: [ 61.189256] 880022c87be8 81177411 0001 [ 61.253133] 3c0c4180 880022c87ba8 [ 61.345334] 880022c87d10 0001 [ 61.459069] Call Trace: [ 61.505273] [] ? __bpf_prog_run+0x7a1/0x1360 [ 61.625511] [] ? update_curr+0x79/0x170 [ 61.741423] [] ? update_cfs_shares+0xbc/0x100 [ 61.837892] [] ? __schedule+0x30d/0x7f0 [ 61.941349] [] ? __schedule+0x301/0x7f0 [ 62.073874] [] ? __schedule+0x30d/0x7f0 [ 62.185260] [] ? __schedule+0x301/0x7f0 [ 62.186239] [] ? __schedule+0x30d/0x7f0 [ 62.305193] [] ? __schedule+0x301/0x7f0 [ 62.399854] [] ? __schedule+0x30d/0x7f0 [ 62.406219] [] ? __schedule+0x301/0x7f0 [ 62.407994] [] ?
[Kernel-packages] [Bug 1755627] Re: ibrs/ibpb fixes result in excessive kernel logging
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755627 Title: ibrs/ibpb fixes result in excessive kernel logging 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 Artful: Fix Committed Bug description: Since at least kernel 4.4.0-116, every invocation of `sysctl -a` results in kernel logs similar to the following: % sysctl -a &>/dev/null; dmesg -T | tail -8 [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0 The output varies with the number of CPUs. After digging a bit, it turns out this is triggered upon every read of `kernel.ibrs_dump`: % for i in {1..3}; do sysctl kernel.ibrs_dump; dmesg -T | tail -8; echo; sleep 1; done kernel.ibrs_dump = 0 [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0 kernel.ibrs_dump = 0 [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0 kernel.ibrs_dump = 0 [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0 Those tests were against an EC2 instance running Ubuntu 4.4.0-116.140-generic 4.4.98 per /proc/version_signature Normally this would not be the biggest concern but we have tooling that gathers instance info on a schedule, including sysctl output, thus resulting in the kernel ring buffer being full of nothing but said output in most cases and hindering live troubleshooting as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764810] Re: Xenial: rfkill: fix missing return on rfkill_init
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764810 Title: Xenial: rfkill: fix missing return on rfkill_init Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: == SRU Justification == A previous backport to bug LP: #1745130 overlooked adding in an error return that was introduced by commit 6124c53edeea. Fix this by adding in the missing return. Detected by CoverityScan, CID#1467925 ("Missing return statement) Fixes: b9a5fffbaee6 ("rfkill: Add rfkill-any LED trigger") == Fix == Add missing return error code == Test == N/A == Regression Potential == Minimal, this fixes the broken backport, so the change is small and restores the original error handling behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765241] Re: virtio_scsi race can corrupt memory, panic kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765241 Title: virtio_scsi race can corrupt memory, panic kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: There's a race in the virtio_scsi driver (for all kernels) That race is inadvertently avoided on most kernels due to a synchronize_rcu call coincidentally placed in one of the racing code paths By happenstance, the set of patches backported to the Ubuntu 4.4 kernel ended up without a synchronize_rcu in the relevant place. The issue first manifests with commit be2a20802abbde04ae09846406d7b670731d97d2 Author: Jan KaraDate: Wed Feb 8 08:05:56 2017 +0100 block: Move bdi_unregister() to del_gendisk() BugLink: http://bugs.launchpad.net/bugs/1659111 The race can cause a kernel panic due to corruption of a freelist pointer in a slab cache. The panics occur in arbitrary places as the failure occurs at an allocation after the corruption of the pointer. However, the most common failure observed has been within virtio_scsi itself during probe processing, e.g.: [3.111628] [] kfree_const+0x22/0x30 [3.112340] [] kobject_release+0x94/0x190 [3.113126] [] kobject_put+0x27/0x50 [3.113838] [] put_device+0x17/0x20 [3.114568] [] __scsi_remove_device+0x92/0xe0 [3.115401] [] scsi_probe_and_add_lun+0x95b/0xe80 [3.116287] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [3.117227] [] ? __pm_runtime_resume+0x5b/0x80 [3.118048] [] __scsi_scan_target+0x10a/0x690 [3.118879] [] scsi_scan_channel+0x7e/0xa0 [3.119653] [] scsi_scan_host_selected+0xf3/0x160 [3.120506] [] do_scsi_scan_host+0x8d/0x90 [3.121295] [] do_scan_async+0x1c/0x190 [3.122048] [] async_run_entry_fn+0x48/0x150 [3.122846] [] process_one_work+0x165/0x480 [3.123732] [] worker_thread+0x4b/0x4d0 [3.124508] [] ? process_one_work+0x480/0x480 Details on the race: CPU A: virtscsi_probe [...] __scsi_scan_target scsi_probe_and_add_lun [on return calls __scsi_remove_device, below] scsi_probe_lun [...] blk_execute_rq blk_execute_rq waits for the completion event, and then on wakeup returns up to scsi_probe_and_all_lun, which calls __scsi_remove_device. In order for the race to occur, the wakeup must occur on a CPU other than CPU B. After being woken up by the completion of the request, the call returns up the stack to scsi_probe_and_add_lun, which calls __scsi_remove_device: __scsi_remove_device blk_cleanup_queue [ no longer calls bdi_unregister ] scsi_target_reap(scsi_target(sdev)) scsi_target_reap_ref_put kref_put kref_sub scsi_target_reap_ref_release scsi_target_destroy ->target_destroy() = virtscsi_target_destroy kfree(tgt) <=== FREE TGT Note that the removal of the call to bdi_unregister in commit xenial be2a20802abbde block: Move bdi_unregister() to del_gendisk() and annotated above is the change that gates whether the issue manifests or not. The other code change from be2a20802abbde has no effect on the race. CPU B: vring_interrupt virtscsi_complete_cmd scsi_mq_done (via ->scsi_done()) scsi_mq_done blk_mq_complete_request __blk_mq_complete_request [...] blk_end_sync_rq complete [ wake up the task from CPU A ] After waking the CPU A task, execution returns up the stack, and then calls atomic_dec(>reqs) in virtscsi_complete_cmd immediately after returning from the call to ->scsi_done. If the activity on CPU A after it is woken up (starting at __scsi_remove_device) finishes before CPU B can call atomic_dec() in virtscsi_complete_cmd, then the atomic_dec() will modify a free list pointer in the freed slab object that contained tgt. This causes the system to panic on a subsequent allocation from the per-cpu slab cache. The call path on CPU B is significantly shorter than that on CPU A after wakeup, so it is likely that an external event delays CPU B. This could be
[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] sky2 ethernet stops working after system resume from suspend. [Fix] Increase the PCI D3 delay can workaround the issue. [Test] User responded that the D3 delay increase can solve the issue. [Regression Potential] Low. It only affects one device. The fix only increase the delay timer, without any functional change. ===Original Bug Report=== After resuming from sleep using the lid-open event, OFTEN (60% replicable, usually after 2nd or later resume) the NIC is not functional, and reloading the sky2 module does not help. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb
[Kernel-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726930 Title: System fails to start (boot) on battery due to read-only root file- system Status in laptop-mode-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Incomplete Status in laptop-mode-tools source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in systemd source package in Xenial: Confirmed Status in laptop-mode-tools source package in Bionic: Confirmed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Incomplete Bug description: This report is to capture the extended diagnostic efforts done on IRC #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was upgraded from 17.04 to 17.10 and since fails to complete start-up of services when powered on battery. We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'" workaround in case this was an ACPI DSDT issue. This appears to be due to a read-only root file-system. What is not clear is how the rootfs goes read-only. The file-system (sda6, ext4) is fsck-ed successfully in the initrd according to the /run/initramfs/fsck.log. From the start-up logs (with "systemd.log_level=debug") we see the ext4 driver report a remount operation not once but five times. $ grep 'EXT4-fs.*sda6' systemd-debug.log Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,data=ordered,commit=600 Those last five appear to be carrying options generated by laptop- mode-tools. User has disabled laptop-mode.service and laptop-mode.timer, and lmt- poll.service, but the issue remains. We see several reports of "read-only file-system": $ grep 'Read-only' systemd-debug.log Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open `/boot/grub/grubenv': Read-only file system. Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to /var/log/gpu-manager.log failed (Read-only file system) Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 'start' task: Read-only file system Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: Read-only file system ... Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of "/var/log/cups" - Read-only file system Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file "/var/log/cups/access_log" - Read-only file system Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open /var/log/lastlog: Read-only file system We also see several problems with systemd's connection to Dbus: $ grep 'Transport endpoint' systemd-debug.log Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit change signal for systemd-logind.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit change signal for lmt-poll.service: Transport endpoint is not connected Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: Transport endpoint
[Kernel-packages] [Bug 1766596] Re: linux-gcp: 4.13.0-1014.18 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed -- 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/1766596 Title: linux-gcp: 4.13.0-1014.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761534] Re: "ip a" command on a guest VM shows UNKNOWN status
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761534 Title: "ip a" command on a guest VM shows UNKNOWN status Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] "ip a" command on a guest VM shows UNKNOWN status. [Test Case] * Environment : Running a guest VM with a virtio-net adaptor interface, running on DPDK. * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example: 2: eth0:mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 . [Regression Potential] * Regression is low, the patch fix the operstate logic for virtio when no VIRTIO_NET_F_STATUS.[1] * The patch has been first accepted in net-next, then move into Linus's git. [1] - VIRTIO_NET_F_STATUS Allow the host to inform us that the link is down by adding a VIRTIO_NET_F_STATUS which indicates that device status is available in virtio_net config. [Other Info] * Linus: https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718 * Net-next: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe [Original Description] It has been brought to our attention the following bug : Environment: The guest VM is using a canonical ubuntu image, and the eth0 is a virtio-net adaptor, running on DPDK. Background: "ip a" command relies on the operstate variable of the net_device structure maintained by the kernel. This is based on the operational state as defined in the IF MIB (RFC 2863). Device drivers are expected to update this member. But many older drivers don’t seem to be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are treated as equal, in some sense, to maintain backward compatibility. Even if we look at https://elixir.free- electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468, the function to check if interface is up, is written as follows, which says that OPER_UNKNOWN is not something to be alarmed about, and just reflective of a state that some drivers don’t care to update about. static inline bool netif_oper_up(const struct net_device *dev) { return (dev->operstate == IF_OPER_UP || dev->operstate == IF_OPER_UNKNOWN /* backward compat */); } Code Ref: 1. https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L1739 2. https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468 3. https://www.kernel.org/doc/Documentation/networking/operstates.txt Now, for traditional kernel mode network adapter drivers, this state is supposed to be manipulated by the driver. And we can safely assume that most current kernel model drivers do keep this updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765698] Re: Unable to insert test_bpf module on Xenial
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765698 Title: Unable to insert test_bpf module on Xenial Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: [SRU Justification] Impact: One of the self-tests which is run by test_bpf will always fail when JIT is turned on, causing the module load to fail. Fix: Picking two patches from upstream will fix this. Testcase: sudo modprobe test_bpf Risk of regression: Minimal, this modifies only a test module, no impact on normal operation. --- With 4.4.0-119, the ubuntu_bpf_jit test will pass: [ 127.177037] test_bpf: Summary: 291 PASSED, 0 FAILED, [0/283 JIT'ed] PASSED: 291 FAILED: 0 But with 4.4.0-121, one test will fail [ 221.361834] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] PASSED: 290 FAILED: 1 stderr: modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ dmesg|grep test_bpf|grep FAIL [ 45.286944] test_bpf: #248 BPF_MAXINSNS: Jump, gap, jump, ... FAIL to prog_create err=-524 len=4096 [ 45.619293] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-121-generic 4.4.0-121.145 ProcVersionSignature: User Name 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 20 12:29 seq crw-rw 1 root audio 116, 33 Apr 20 12:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Apr 20 12:32:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-121-generic N/A linux-backports-modules-4.4.0-121-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766599] Re: linux-oem: 4.13.0-1025.28 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** 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: 1766592 phase: Uploaded + kernel-stable-phase-changed:Friday, 27. April 2018 19:07 UTC + kernel-stable-phase:Promoted to 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: 1766592 - phase: Uploaded - kernel-stable-phase-changed:Friday, 27. April 2018 19:07 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1766599 Title: linux-oem: 4.13.0-1025.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766604] Re: linux: 4.4.0-123.147 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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: bug 1766605 (linux-aws), bug 1766607 (linux-lts-xenial) derivatives: bug 1766608 (linux-snapdragon), bug 1766610 (linux-kvm), bug 1766611 (linux-euclid), bug 1766612 (linux-raspi2), bug 1766614 (linux-aws) - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 25. April 2018 10:01 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase-changed:Friday, 27. April 2018 19:11 UTC + kernel-stable-phase:Promoted to 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: bug 1766605 (linux-aws), bug 1766607 (linux-lts-xenial) derivatives: bug 1766608 (linux-snapdragon), bug 1766610 (linux-kvm), bug 1766611 (linux-euclid), bug 1766612 (linux-raspi2), bug 1766614 (linux-aws) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase-changed:Friday, 27. April 2018 19:11 UTC - kernel-stable-phase:Promoted to proposed + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766604 Title: linux: 4.4.0-123.147 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1766605 (linux-aws), bug 1766607 (linux-lts-xenial) derivatives: bug 1766608 (linux-snapdragon), bug 1766610 (linux-kvm), bug 1766611 (linux-euclid), bug 1766612 (linux-raspi2), bug 1766614 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
v2 SRU request for Artful: https://lists.ubuntu.com/archives/kernel-team/2018-April/092024.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == Commit 52df157f17e5 introduced a regression in v4.13-rc1. This regression causes a stack trace to occur when tearing down an LXD container. The process hangs with the following message: "unregister_netdevice: waiting for eth0 to become free. Usage count = 5" This regression is fixed by commit 510c321b5571, which is in mainline as of v4.16-rc7. The fix is needed in Artful and Bionic. However, Artful needs a prereq commit, so it's SRU request will be sent separately. == Fix == 510c321b5571 ("xfrm: reuse uncached_list to track xdsts") == Regression Potential == Low. This commit is to fix a current regression. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. This occurs when tearing down an LXD container. LXD monitor process hangs with the following stack: $ sudo cat /proc/27043/stack [] msleep+0x2e/0x40 [] netdev_run_todo+0x11f/0x310 [] rtnetlink_rcv+0x2d/0x30 [] netlink_unicast+0x18c/0x240 [] netlink_sendmsg+0x2dd/0x3c0 [] sock_sendmsg+0x38/0x50 [] ___sys_sendmsg+0x2e3/0x2f0 [] __sys_sendmsg+0x54/0x90 [] SyS_sendmsg+0x12/0x20 [] do_syscall_64+0x5b/0xc0 [] entry_SYSCALL64_slow_path+0x8/0x8 [] 0x Issue submitted to LXD as well ([1]), though as indicated there, it seems to be a kernel bug. [1] https://github.com/lxc/lxd/issues/4208 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jan 31 11:42:59 2018 InstallationDate: Installed on 2016-11-09 (447 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751990] Re: problems with kernel 4.13
add kernel parameter "blacklist=nouveau modprobe.blacklist=nouveau" will help to boot up for kernel 4.13 and 4.16, but does not solve nvidia 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/1751990 Title: problems with kernel 4.13 Status in linux package in Ubuntu: Confirmed Bug description: I have a laptop call dc pro. it is made in china. processor is Intel(R) Pentium(R) CPU G4560 @ 3.50GHz. with nvidia gtx 1050. The problems are: 1 the ubuntu 16.04.03 installation will hang somewhere. luckily 16.04.02 will go through. 2 the system will not boot after upgrade to kernel 4.13. the old kernel 4.8 will boot without problem. 3 After install the cuda 9.1 both kernel will boot, but nvidia did not come into play(lsmod shows no nv, no nvidia-smi command, only 3 nvidia commands left "nvidia-detector nvidia-modprobe nvidia-settings" ) for the kernel 4.13, the old kernel 4.8 is ok though ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.24 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue Feb 27 13:39:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-17 (10 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weilo 1661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=448239a6-97f0-4285-95a8-ca7abb71c697 InstallationDate: Installed on 2018-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shinelon Computer W65KJ1_KK1 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic root=UUID=e000d41d-996e-45e2-bf04-d0307aaa6e36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65KJ1_KK1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnShinelonComputer:pnW65KJ1_KK1:pvrNotApplicable:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: W65KJ1_KK1 dmi.product.version: Not Applicable dmi.sys.vendor: Shinelon Computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762812] Re: /dev/ipmi enumeration flaky on Cavium Sabre nodes
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762812 Title: /dev/ipmi enumeration flaky on Cavium Sabre nodes Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). *** Note that systems need to be running firmware 6.2 or greater *** [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763271] Re: [8086:3e92] display becomes blank after S3
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- 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/1763271 Title: [8086:3e92] display becomes blank after S3 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: [Impact] The display becomes black after S3 with the following error messages. dmesg: [ 60.546305] [drm:intel_dp_start_link_train [i915]] Link Training failed at link rate = 54, lane count = 4 Xorg.0.log: [ 60.748] (EE) modeset(0): failed to set mode: Invalid argument [ 60.748] (WW) modeset(0): hotplug event: connector 48's link-state is BAD, tried resetting the current mode. You may be left with a black screen if this fails... [Fix] Looks like link training fallback fails sometimes with eDP, we need this commit to fix the issue. commit a306343bcd7df89d9d45a601929e26866e7b7a81 (refs/bisect/bad) Author: Manasi NavareDate: Thu Oct 12 12:13:38 2017 -0700 drm/i915/edp: Do not do link training fallback or prune modes on EDP [Regression Potential] Should be low. To avoid conflicts, we introduce 4 commits, I'll try explaining them below a306343 drm/i915/edp: Do not do link training fallback or prune modes on EDP This is the fix commit and the behavior only changes when DP is eDP, it does nothing if DP is eDP. Should be fine to not do link training fallback and not emit Hotplug Uevent to userspace to start modeset, since its eDP, the display is fixed. 1853a9d drm/i915/dp: make is_edp non-static and rename to intel_dp_is_edp 7b91bf7 drm/i915/dp: rename intel_dp_is_edp to intel_dp_is_port_edp Above 2 commits do function name renaming only. dc911f5 drm/i915/edp: Allow alternate fixed mode for eDP if available. Change the prototype of function "intel_panel_init()" and adding one extra argument, should have small impact on the display. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1763271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760712] Re: perf vendor events arm64: Enable JSON events for ThunderX2 B0
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760712 Title: perf vendor events arm64: Enable JSON events for ThunderX2 B0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] We enabled ThunderX2 vendor events in LP: #1747523. That was sufficient for A2 silicon, but needs an update to recognize B0 silicon. [Test Case] Successful output on ThunderX2 B0 silicon: $ sudo perf list | grep thunderx2 thunderx2 imp def: $ [Regression Risk] This teaches existing code about a new SoC, which should mitigate regressions for all other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761104] Re: fix regression in mm/hotplug, allows NVIDIA driver to work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761104 Title: fix regression in mm/hotplug, allows NVIDIA driver to work Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Fix Committed Bug description: == SRU Justification, ARTFUL == Bug fix #1747069 causes an issue for NVIDIA drivers on ppc64el platforms. According to Will Davis at NVIDIA: "- The original patch 3d79a728f9b2e6ddcce4e02c91c4de1076548a4c changed the call to arch_add_memory in mm/memory_hotplug.c to call with the boolean argument set to true instead of false, and inverted the semantics of that argument in the arch layers. - The revert patch 4fe85d5a7c50f003fe4863a1a87f5d8cc121c75c reverted the semantic change in the arch layers, but didn't revert the change to the arch_add_memory call in mm/memory_hotplug.c" And also: "It looks like the problem here is that the online_type is _MOVABLE but can_online_high_movable(nid=255) is returning false: if ((zone_idx(zone) > ZONE_NORMAL || online_type == MMOP_ONLINE_MOVABLE) && !can_online_high_movable(pfn_to_nid(pfn))) This check was removed by upstream commit 57c0a17238e22395428248c53f8e390c051c88b8, and I've verified that if I apply that commit (partially) to the 4.13.0-37.42 tree along with the previous arch_add_memory patch to make the probe work, I can fully online the GPU device memory as expected. Commit 57c0a172.. implies that the can_online_high_movable() checks weren't useful anyway, so in addition to the arch_add_memory fix, does it make sense to revert the pieces of 4fe85d5a7c50f003fe4863a1a87f5d8cc121c75c that added back the can_online_high_movable() check?" == Fix == Fix partial backport from bug #1747069, remove can_online_high_movable and fix the incorrectly set boolean argument to arch_add_memory(). == Testing == run ADT memory hotplug test, should not regress this. Without the fix, the nvidia driver on powerpc will not load because it cannot map memory for the device. With the fix it loads. == Regression Potential == This fixes a regression in the original fix and hence the regression potential is the same as the previously SRU'd bug fix for #1747069, namely: "Reverting this commit does remove some functionality, however this does not regress the kernel compared to previous releases and having a working reliable memory hotplug is the preferred option. This fix does touch some memory hotplug, so there is a risk that this may break this functionality that is not covered by the kernel regression testing." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755627] Re: ibrs/ibpb fixes result in excessive kernel logging
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755627 Title: ibrs/ibpb fixes result in excessive kernel logging 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 Artful: Fix Committed Bug description: Since at least kernel 4.4.0-116, every invocation of `sysctl -a` results in kernel logs similar to the following: % sysctl -a &>/dev/null; dmesg -T | tail -8 [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0 The output varies with the number of CPUs. After digging a bit, it turns out this is triggered upon every read of `kernel.ibrs_dump`: % for i in {1..3}; do sysctl kernel.ibrs_dump; dmesg -T | tail -8; echo; sleep 1; done kernel.ibrs_dump = 0 [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0 kernel.ibrs_dump = 0 [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0 kernel.ibrs_dump = 0 [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0 [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0 [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4 [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0 [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0 Those tests were against an EC2 instance running Ubuntu 4.4.0-116.140-generic 4.4.98 per /proc/version_signature Normally this would not be the biggest concern but we have tooling that gathers instance info on a schedule, including sysctl output, thus resulting in the kernel ring buffer being full of nothing but said output in most cases and hindering live troubleshooting as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761534] Re: "ip a" command on a guest VM shows UNKNOWN status
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761534 Title: "ip a" command on a guest VM shows UNKNOWN status Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: [Impact] "ip a" command on a guest VM shows UNKNOWN status. [Test Case] * Environment : Running a guest VM with a virtio-net adaptor interface, running on DPDK. * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example: 2: eth0:mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 . [Regression Potential] * Regression is low, the patch fix the operstate logic for virtio when no VIRTIO_NET_F_STATUS.[1] * The patch has been first accepted in net-next, then move into Linus's git. [1] - VIRTIO_NET_F_STATUS Allow the host to inform us that the link is down by adding a VIRTIO_NET_F_STATUS which indicates that device status is available in virtio_net config. [Other Info] * Linus: https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718 * Net-next: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe [Original Description] It has been brought to our attention the following bug : Environment: The guest VM is using a canonical ubuntu image, and the eth0 is a virtio-net adaptor, running on DPDK. Background: "ip a" command relies on the operstate variable of the net_device structure maintained by the kernel. This is based on the operational state as defined in the IF MIB (RFC 2863). Device drivers are expected to update this member. But many older drivers don’t seem to be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are treated as equal, in some sense, to maintain backward compatibility. Even if we look at https://elixir.free- electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468, the function to check if interface is up, is written as follows, which says that OPER_UNKNOWN is not something to be alarmed about, and just reflective of a state that some drivers don’t care to update about. static inline bool netif_oper_up(const struct net_device *dev) { return (dev->operstate == IF_OPER_UP || dev->operstate == IF_OPER_UNKNOWN /* backward compat */); } Code Ref: 1. https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L1739 2. https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468 3. https://www.kernel.org/doc/Documentation/networking/operstates.txt Now, for traditional kernel mode network adapter drivers, this state is supposed to be manipulated by the driver. And we can safely assume that most current kernel model drivers do keep this updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758507 Title: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] sky2 ethernet stops working after system resume from suspend. [Fix] Increase the PCI D3 delay can workaround the issue. [Test] User responded that the D3 delay increase can solve the issue. [Regression Potential] Low. It only affects one device. The fix only increase the delay timer, without any functional change. ===Original Bug Report=== After resuming from sleep using the lid-open event, OFTEN (60% replicable, usually after 2nd or later resume) the NIC is not functional, and reloading the sky2 module does not help. Relevant parts from dmesg: [ 582.852065] sky2 :04:00.0: Refused to change power state, currently in D3 ... [ 827.613729] sky2 :04:00.0: ignoring stuck error report bit [ 827.613748] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613750] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613752] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613754] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613756] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613759] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613761] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613763] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613765] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613767] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613769] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613772] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613774] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613776] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613778] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613780] sky2 :04:00.0: enp4s0: phy I/O error [ 827.613782] sky2 :04:00.0: enp4s0: phy I/O error And after reloading the module: [ 1421.781480] sky2: driver version 1.30 [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003) [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff [ 1421.782292] sky2: probe of :04:00.0 failed with error -95 Possibly relevant: [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID. Replicability: When it happens once, further suspend-resume cycles (tried ~5) don't fix it. Reboot fixes the NIC, and it often survives first resume after that, but 1-2 suspend-resume cycles later the issue WILL occur again. Per-boot chance of encountering the issue - so far 2/5. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-12-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sat Mar 24 09:54:10 2018 HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1 InstallationDate: Installed on 2018-03-21 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb
[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- 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/1762693 Title: No network with e1000e driver on 4.13.0-38-generic Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: ===SRU Justification=== [Impact] e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem. The regression was introduced by patches in LP: #1730550. [Fix] Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue. e1000e now reports correct link status. [Test] With the extra commit, the e1000e starts to working again. [Regression Potential] Low. It says: Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up") So it's pretty clear this patch is to fix the regression. It's in upstream linux-stable, so only Arftul needs this patch. ===Original Bug Report=== When my computer boots with the most recent kernel 4.13.0-38-generic, I don't have a working network connection. ethtool reports that my network interface doesn't have a connection: martin@dogmeat ~ % cat ethtool.txt Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 2 Transceiver: internal Auto-negotiation: on MDI-X: Unknown (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: no dmesg contains suspicious e1000e error messages: martin@dogmeat ~ % tail -n 40 dmesg.txt [ 20.211715] Could not find valid key in user session keyring for sig specified in mount option: [459a10809c211381] [ 20.211716] One or more global auth toks could not properly register; rc = [-2] [ 20.211717] Error parsing options; rc = [-2] [ 25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 51.244686] ahci :00:17.0: port does not support device sleep [ 56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492 [ 83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500 [ 88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 88.938939]
[Kernel-packages] [Bug 1765850] Re: arm64: fix CONFIG_DEBUG_WX address reporting
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765850 Title: arm64: fix CONFIG_DEBUG_WX address reporting Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: [Impact] The warnings emitted by the kernel when CONFIG_DEBUG_WX is enabled will show an incorrect address, nullifying the value of this config option. [Test Case] Boot; if a "arm64/mm: Found insecure W+X mapping at address" message appears, confirm it's not in the userspace mapping. [Regression Risk] This is arm64-only code, so regressions would be restricted to arm64. This change is currently present in bionic without any noticed regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766592] Re: linux: 4.13.0-40.45 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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: bug 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem) derivatives: bug 1766593 (linux-raspi2) - kernel-stable-phase-changed:Wednesday, 25. April 2018 08:30 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase-changed:Friday, 27. April 2018 19:01 UTC + kernel-stable-phase:Promoted to 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: bug 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem) derivatives: bug 1766593 (linux-raspi2) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase-changed:Friday, 27. April 2018 19:01 UTC - kernel-stable-phase:Promoted to proposed + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766592 Title: linux: 4.13.0-40.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: 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 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem) derivatives: bug 1766593 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765977] Re: HiSilicon HNS NIC names are truncated in /proc/interrupts
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765977 Title: HiSilicon HNS NIC names are truncated in /proc/interrupts Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: In Progress Bug description: [Impact] HiSilicon HNS NIC names are truncated in /proc/interrupts, making it difficult for an admin to associate activity among adapters in the system. [Test Case] $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //' Without the fix: enahisic2i0-tx0 enahisic2i0-tx1 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 With the fix: enahisic2i0-tx0 enahisic2i0-tx1 enahisic2i0-tx2 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx10 enahisic2i0-tx11 enahisic2i0-tx12 enahisic2i0-tx13 enahisic2i0-tx14 enahisic2i0-tx15 [Regression Risk] Upstream patch, restricted to a single driver for a system we can directly test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-April/092020.html ** Description changed: + == SRU Justification == + Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers, + which violates the e1000e specification. Specifically, the driver + configures auto-clearing of the "OTHER" interrupt types, and the "OTHER" interrupt + handler expects to see an uncleared interrupt source for the "OTHER" types; + consequently, the link state change interrupts are not identified by the driver, + and thus the virtual E1000e device doesn't function correctly inside VMware VMs. + + This patch Fixes: 4aea7a5c5e94 ("e1000e: Avoid receiver overrun + interrupt bursts") + + == Fix == + 745d0bd3af99 ("e1000e: Remove Other from EIAC") + + == Regression Potential == + Low. Fixes an existing regression and limited to e1000e driver. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + + == Original Bug Description == Hi Ubuntu folks, Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers, which violates the e1000e specification. Specifically, the driver configures auto-clearing of the "OTHER" interrupt types, and the "OTHER" interrupt handler expects to see an uncleared interrupt source for the "OTHER" types; consequently, the link state change interrupts are not identified by the driver, and thus the virtual E1000e device doesn't function correctly inside VMware VMs. I have verified that Linux kernel 4.16.2 has fixed the issues and our on-perm QE has verified 4.16-RC functions correctly inside VMware VMs. Could you please crossport the fix from linux-4.16 into Ubuntu 18.04 that would be frozen in 2 days? Here are the change history: https://lkml.org/lkml/2018/3/25/248 Benjamin Poirier (7): e1000e: Remove Other from EIAC Partial revert "e1000e: Avoid receiver overrun interrupt bursts" e1000e: Fix queue interrupt re-raising in Other interrupt e1000e: Avoid missed interrupts following ICR read e1000e: Fix check_for_link return value with autoneg off Revert "e1000e: Separate signaling for link check/link up" e1000e: Fix link check race condition Thanks, -zheng -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764892 Title: e1000e msix interrupts broken in linux-image-4.15.0-15-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers, which violates the e1000e specification. Specifically, the driver configures auto-clearing of the "OTHER" interrupt types, and the "OTHER" interrupt handler expects to see an uncleared interrupt source for the "OTHER" types; consequently, the link state change interrupts are not identified by the driver, and thus the virtual E1000e device doesn't function correctly inside VMware VMs. This patch Fixes: 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts") == Fix == 745d0bd3af99 ("e1000e: Remove Other from EIAC") == Regression Potential == Low. Fixes an existing regression and limited to e1000e driver. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == Hi Ubuntu folks, Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers, which violates the e1000e specification. Specifically, the driver configures auto-clearing of the "OTHER" interrupt types, and the "OTHER" interrupt handler expects to see an uncleared interrupt source for the "OTHER" types; consequently, the link state change interrupts are not identified by the driver, and thus the virtual E1000e device doesn't function correctly inside VMware VMs. I have verified that Linux kernel 4.16.2 has fixed the issues and our on-perm QE has verified 4.16-RC functions correctly inside VMware VMs. Could you please crossport the fix from linux-4.16 into Ubuntu 18.04 that would be frozen in 2 days? Here are the change history: https://lkml.org/lkml/2018/3/25/248 Benjamin Poirier (7): e1000e: Remove Other from EIAC Partial revert "e1000e: Avoid receiver overrun interrupt bursts" e1000e: Fix queue interrupt re-raising in Other interrupt e1000e: Avoid missed interrupts following ICR read e1000e: Fix check_for_link return value with autoneg off Revert "e1000e: Separate signaling for link check/link up" e1000e: Fix link check race condition Thanks, -zheng To manage notifications about this bug go to:
[Kernel-packages] [Bug 1766596] Re: linux-gcp: 4.13.0-1014.18 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1766592 phase: Uploaded + kernel-stable-phase-changed:Friday, 27. April 2018 18:33 UTC + kernel-stable-phase:Promoted to 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: 1766592 - phase: Uploaded - kernel-stable-phase-changed:Friday, 27. April 2018 18:33 UTC - kernel-stable-phase:Promoted to proposed + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1766596 Title: linux-gcp: 4.13.0-1014.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed 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: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1766592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764980] Re: test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM kernel
Hi Po-Hsu, Thanks for double-checking, that's appreciated! The security team does not have an opinion on whether CONFIG_KALLSYMS and CONFIG_KALLSYMS_ALL should be enabled, from a security/hardening standpoint. It may be useful from the kernel team's perspective, to make debugging kernel oops bug reports easier. Thanks again! ** Changed in: qa-regression-testing Status: Fix Committed => Fix Released -- 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/1764980 Title: test_095_kernel_symbols_missing_proc_modules failed with 4.15 KVM kernel Status in QA Regression Testing: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: test_095_kernel_symbols_missing_proc_modules from ubuntu_qrt_kernel_security test failed with 4.15.0-1004-kvm FAIL: test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest) kernel addresses in /proc/modules are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1609, in test_095_kernel_symbols_missing_proc_modules self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) File "./test-kernel-security.py", line 1492, in _check_pK_files test_function(expected_restricted) File "./test-kernel-security.py", line 1525, in _095_kernel_symbols_missing_proc_modules expected) File "./test-kernel-security.py", line 1414, in _read_twice self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, address)) AssertionError: /proc/modules: root saw 0x ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Wed Apr 18 09:00:43 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1764980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766054] Re: Acer Swift sf314-52 power button not managed
SRU Requests: https://lists.ubuntu.com/archives/kernel-team/2018-April/092013.html https://lists.ubuntu.com/archives/kernel-team/2018-April/092016.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766054 Title: Acer Swift sf314-52 power button not managed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level: [405.267887] acer_wmi: Unknown key number - 0x87] This patch adds the KEY_POWER event in acer-wmi. The patch will also be sent upstream, but it is being requested in Ubuntu to not wait for it to come back downstream. This patch is also needed in Xenial, but Xenial requres a minor backport. == Fix == UBUNTU: SAUCE: platform/x86: acer-wmi: add another KEY_POWER keycode == Regression Potential == Low. This is a oneliner that addes a new keymap. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level [405.267887] acer_wmi: Unknown key number - 0x87] I develop and test on Acer Swift sf314-52 a patch that fix the issue adding the KEY_POWER event in acer-wmi. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest
ppc64el versions of the Xenial test kernel are now available here: http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial Xenial required the following two prereq commits: d96f234f47af ("powerpc: Avoid load hit store in setup_sigcontext()") d11994314b2b ("powerpc: signals: Stop using current in signal code") -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762928 Title: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Released Bug description: ---Problem Description--- tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] guests on a P9 host running bionic final beta version. Contact Information = srikanth/bssrika...@in.ibm.com ---uname output--- 16.04.04 Guest running in P8compat mode: Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 18.04 guest running in P8compat mode: Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Log into P9 Ubuntu 18.04 host, take console of guest `srikanth_ubuntu160404` 2. Run TM selftests git clone --depth 1 https://github.com/torvalds/linux.git;cd linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm run_tests We will observe one of the tm tests failing, mentioned below: selftests: tm-trap test: tm_trap_test tags: git_version:c18bb39 Little-Endian machine detected. Checking if endianness flips inadvertently on trap in TM... yes! failure: tm_trap_test not ok 1..11 selftests: tm-trap [FAIL] Expected result: All tm selftests should have been pass on the P8 compat guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host kernel Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for srikanth/bssrika...@in.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #2 - SRIKANTH AITHAL- 2018-04-10 01:32:00 == == Comment: #3 - SRIKANTH AITHAL - 2018-04-10 01:33:41 == == Comment: #4 - SRIKANTH AITHAL - 2018-04-10 01:34:02 == Please pick `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")` ie. the commit that the test was written for To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
I built a test kernel with the two commits pointed out by Jay. The test kernel also required commit f307668bfc as a prereq. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1753662 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767452] [NEW] kernel oops when I undocked
Public bug reported: Here's a snippet from the kernel log which I think will make the actual issue clear: Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused to change power state, currently in D3 Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, device number 2 Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB bus 6 deregistered Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, device number 3 Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, device number 4 Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, device number 5 Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, device number 7 Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host halt failed, -19 Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host not accessible, reset failed. Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB bus 5 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: remove, state 4 Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB bus 4 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: remove, state 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, device number 2 Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, device number 3 Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, device number 4 Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel NULL pointer dereference at 0034 Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: tty_unregister_driver+0xd/0x70 Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops: [#1] SMP PTI Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel joydev uvcvideo input_leds Apr 27 09:49:21 caliburn kernel: [ 4559.464233] serio_raw snd_hda_codec thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei ucsi_acpi typec_ucsi intel_pch_thermal typec shpchp soundcore tpm_crb mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd e1000e glue_helper cryptd syscopyarea psmouse sysfillrect sysimgblt nvme ptp fb_sys_fops pps_core thunderbolt nvme_core drm rtsx_pci wmi i2c_hid Apr 27 09:49:21 caliburn kernel: [ 4559.464273] video hid Apr 27 09:49:21 caliburn kernel: [ 4559.464276] CPU: 1 PID: 3 Comm: kworker/u8:1 Not tainted 4.15.0-20-generic #21-Ubuntu Apr 27 09:49:21 caliburn kernel: [ 4559.464278] Hardware name: LENOVO 20HR000FUS/20HR000FUS, BIOS N1MET39W (1.24 ) 09/27/2017
[Kernel-packages] [Bug 1767452] Re: kernel oops when I undocked
Here's the above in an (unmunged) attachment ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5128741/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767452 Title: kernel oops when I undocked Status in linux-signed package in Ubuntu: New Bug description: Here's a snippet from the kernel log which I think will make the actual issue clear: Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused to change power state, currently in D3 Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, device number 2 Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB bus 6 deregistered Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: remove, state 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, device number 1 Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, device number 3 Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, device number 4 Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, device number 5 Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, device number 7 Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host halt failed, -19 Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host not accessible, reset failed. Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB bus 5 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: Refused to change power state, currently in D3 Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: remove, state 4 Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB bus 4 deregistered Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI host controller not responding, assume dead Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: remove, state 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, device number 1 Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, device number 2 Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, device number 3 Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, device number 4 Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel NULL pointer dereference at 0034 Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: tty_unregister_driver+0xd/0x70 Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops: [#1] SMP PTI Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel joydev uvcvideo input_leds Apr 27 09:49:21 caliburn kernel: [ 4559.464233] serio_raw snd_hda_codec thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei ucsi_acpi typec_ucsi intel_pch_thermal typec shpchp soundcore tpm_crb mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel
[Kernel-packages] [Bug 1766054] Re: Acer Swift sf314-52 power button not managed
** Description changed: - It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). + == SRU Justification == + It's impossible to use power button functionalities in Acer Swift Notebook + Series (tested on Acer Swift 3 sf314-52). The keyboard button is not + managed at acer-wmi level: + + [405.267887] acer_wmi: Unknown key number - 0x87] + + This patch adds the KEY_POWER event in acer-wmi. The patch will also be sent + upstream, but it is being requested in Ubuntu to not wait for it to come back + downstream. This patch is also needed in Xenial, but Xenial requres a minor backport. + + == Fix == + UBUNTU: SAUCE: platform/x86: acer-wmi: add another KEY_POWER keycode + + == Regression Potential == + Low. This is a oneliner that addes a new keymap. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + + It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level [405.267887] acer_wmi: Unknown key number - 0x87] I develop and test on Acer Swift sf314-52 a patch that fix the issue adding the KEY_POWER event in acer-wmi. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766054 Title: Acer Swift sf314-52 power button not managed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level: [405.267887] acer_wmi: Unknown key number - 0x87] This patch adds the KEY_POWER event in acer-wmi. The patch will also be sent upstream, but it is being requested in Ubuntu to not wait for it to come back downstream. This patch is also needed in Xenial, but Xenial requres a minor backport. == Fix == UBUNTU: SAUCE: platform/x86: acer-wmi: add another KEY_POWER keycode == Regression Potential == Low. This is a oneliner that addes a new keymap. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. It's impossible to use power button functionalities in Acer Swift Notebook Series (tested on Acer Swift 3 sf314-52). The keyboard button is not managed at acer-wmi level [405.267887] acer_wmi: Unknown key number - 0x87] I develop and test on Acer Swift sf314-52 a patch that fix the issue adding the KEY_POWER event in acer-wmi. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767443] Re: regular hard lockup on bionic kernel
FWIW, I verified that Tycho's microcode revision is what's expected for his CPU: 142: sig 0x000306d4, pf mask 0xc0, 2018-01-18, rev 0x002a, size 18432 I don't think his lockups are due to running a previously published microcode revision that Intel pulled or any bad interactions with the 4.15 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767443 Title: regular hard lockup on bionic kernel Status in linux-signed package in Ubuntu: New Bug description: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766614] Re: linux-aws: 4.4.0-1056.65 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1766614 Title: linux-aws: 4.4.0-1056.65 -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 promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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: 1766604 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766605] Re: linux-aws: 4.4.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1766605 Title: linux-aws: 4.4.0-1018.18 -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 promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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: 1766604 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"
OK, i'm now running the V4.16.0 kernel: > craigster0@p51:/local/home/craigster0/Downloads/linux-kernel-4.16$ uname -r > 4.16.0-041600-generic and clicking on the "speaker icon" on the menu bar at the bottom of the screen still shows "No output or input devices found". more importantly, trying to play audio with Amarok or Rhythmbox produces no audible signal. to the best of my recollection. i don't think this problem was _caused_ by a kernel update. both speakers and microphone worked fine with all apps before i performed a software update, and failed after that. the trick is figuring out exactly which software update caused 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/1761051 Title: laptop sound broken in latest update -- "No output or input devices found" Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: after i installed the latest update for Kubuntu 17.10 my audio devices disappeared and i lost the ability to listen to music or play sounds on my laptop. it worked fine before the update! (Caveat: sometimes ads or youtube will play through the speakers or headphones but it is unpredictable and i have no control over volume or muting.) the Plasma Audio Volume settings show "No Output Devices Available" and "No Input Devices Available". it worked fine before the last update. this is a Lenovo P51, a fairly popular laptop for linux. my laptop is a high end version with an E3-1505M CPU and "hybrid graphics". i do not update the software every day so the problem may have been introduced upto two weeks ago, but no earlier then that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE Date: Tue Apr 3 21:38:36 2018 HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02 InstallationDate: Installed on 2018-01-12 (81 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: LENOVO 20HHCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET31W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW 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:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767443] Re: regular hard lockup on bionic kernel
Here's /var/log/kern.log, just for grins. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443/+attachment/5128706/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767443 Title: regular hard lockup on bionic kernel Status in linux-signed package in Ubuntu: New Bug description: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766599] Re: linux-oem: 4.13.0-1025.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) ** Changed in: kernel-sru-workflow/promote-to-proposed 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/1766599 Title: linux-oem: 4.13.0-1025.28 -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: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa 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 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: 1766592 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767443] [NEW] regular hard lockup on bionic kernel
Public bug reported: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1767443 Title: regular hard lockup on bionic kernel Status in linux-signed package in Ubuntu: New Bug description: Hi guys, I'm sorry I have no real information to add to this, but Serge encouraged me to file a bug to get you guys to help me to debug this, so blame him. I've been running the bionic kernels on a thinkpad X1 carbon 3rd generation for several months, and experiencing 2x hard lockups per day. Nothing in /var/log/kern.log looks very obvious to me, and I'm not lucky enough to get a stack trace or anything. Attached are the `ubuntu-bug linux` things that are uploaded automatically, but I'm happy to do whatever science experiments are necessary to get further info. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 10:45:49 2018 InstallationDate: Installed on 2017-11-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766610] Re: linux-kvm: 4.4.0-1022.27 -proposed tracker
One comment for future releases: would be nice if config changes could be better documented in the changelog and/or attached bugs - listing which exact flags have been changed to resolve the respective bug. But that's just a thing from my wishlist. ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1766610 Title: linux-kvm: 4.4.0-1022.27 -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 promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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: 1766604 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766596] Re: linux-gcp: 4.13.0-1014.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1766596 Title: linux-gcp: 4.13.0-1014.18 -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 promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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: 1766592 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766006] Re: kworker taking 100% cpu one one single core
** 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/1766006 Title: kworker taking 100% cpu one one single core Status in linux package in Ubuntu: Confirmed Bug description: kworker is taking 100% cpu on a single core leaving the other cores free on 6670HQ on Asus G752VT. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Apr 21 15:04:58 2018 InstallationDate: Installed on 2018-04-21 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anil 1714 F pulseaudio /dev/snd/controlC0: anil 1714 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ea11b388-87d0-43a7-a834-e5177fb29d2c InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. G752VT Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-39-generic N/A linux-backports-modules-4.13.0-39-generic N/A linux-firmware 1.157.17 Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G752VT.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G752VT 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.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G752VT 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/1766006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
Thanks for the pointer, Jay! I'll build a Xenial test kernel with these two commits and post a link to 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/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766610] Re: linux-kvm: 4.4.0-1022.27 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1766610 Title: linux-kvm: 4.4.0-1022.27 -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 promote-to-proposed series: In Progress 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 series: New Status in Kernel SRU Workflow verification-testing series: New 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: 1766604 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Wow, I just upgraded to 18.04 and after the restart bluetooth was gone. I tried to restart a couple of times, no deal, then I turned off and on again, and it worked! My device is this one: Bus 001 Device 005: ID 0cf3:e007 Atheros Communications, Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JH 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:
[Kernel-packages] [Bug 1767396] [NEW] Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support
Private bug reported: Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support Quickbooks toll free number + 1-844-366-8247 .Quickbooks Errors Support At the time of upgrading QuickBooks to the next version or updating files with information you might encounter messages labeled with error codes, which might interfere with the flow of your work. To resolve 6000, H505, H202, 3371, 6123,1603, 15215 and more critical errors contact our technical experts having extensive knowledge about the software through toll free number + 1-844-366-8247 .Quickbooks Errors Support Common Quickbooks Repairable Problems Error: -6147,0: This is not a QuickBooks data file or there is a problem with the data file Quickbooks Connection has been Lost How to resolve the 'Quickbooks Connection Lost' error message? QuickBooks has Experienced a Problem and Must be Shut Down An error occurred when Quickbooks tried to access the company file. Unrecoverable Error, Quickbooks must shut down Some Sales Orders or Estimates may be incorrectly marked as closed or display incorrect invoiced quantities Quickbooks Rebuild or Verify Errors Error in reload.sql at line xxx Quickbooks Error Code -6000, -82 | 80070057 Quickbooks Error Code -6000,-301: An error occurred when QuickBooks tried to access the company file. Quickbooks Error Code -6150, -1004 Abnormal program termination Runtime Error! Program QBW32.EXE Microsoft Visual C++ Runtime Library Item has missing rows in the item history table Get Decrypted Credit Card Number decryption has failed intuit™ 1-(844) 366 8247 Quickbooks tech support phone number QuickBooks™ phone number(1844)-366-8247) QuickBooks phone number WSA Find all the basic information you need for your Intuit product or service at Intuit Support or call 1(8oo) 366-o992 (QB INTUIT). Quickbooks Phone Number (1844 366-8247), Quickbooks support phone number, Quickbooks support number, Quickbooks tech support number, Quickbooks tech support phone number, Quickbooks technical support number, Quickbooks technical support phone number, Quickbooks customer service phone number, Quickbooks customer support number, Quickbooks customer care number, Quickbooks customer care phone number, Quickbooks customer service phone number, Quickbooks customer service number, Quickbooks help number, Quickbooks help phone number, Quickbooks help desk phone number, Quickbooks help desk number, Quickbooks helpline number, Quickbooks helpline phone number, Quickbooks toll free number, Quickbooks toll free phone number, Quickbooks telephone number, Quickbooks support telephone number, Quickbooks tech support telephone number, Quickbooks technical support telephone number, Quickbooks customer service telephone number, Quickbooks customer care telephone number, Quickbooks help telephone number, Quickbooks 8oo phone number, Quickbooks 8oo number, ** Affects: null-and-void Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767396 Title: Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support Status in NULL Project: Invalid Bug description: Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support Quickbooks toll free number + 1-844-366-8247 .Quickbooks Errors Support At the time of upgrading QuickBooks to the next version or updating files with information you might encounter messages labeled with error codes, which might interfere with the flow of your work. To resolve 6000, H505, H202, 3371, 6123,1603, 15215 and more critical errors contact our technical experts having extensive knowledge about the software through toll free number + 1-844-366-8247 .Quickbooks Errors Support Common Quickbooks Repairable Problems Error: -6147,0: This is not a QuickBooks data file or there is a problem with the data file Quickbooks Connection has been Lost How to resolve the 'Quickbooks Connection Lost' error message? QuickBooks has Experienced a Problem and Must be Shut Down An error occurred when Quickbooks tried to access the company file. Unrecoverable Error, Quickbooks must shut down Some Sales Orders or Estimates may be incorrectly marked as closed or display incorrect invoiced quantities Quickbooks Rebuild or Verify Errors Error in reload.sql at line xxx Quickbooks Error Code -6000, -82 | 80070057 Quickbooks Error Code -6000,-301: An error occurred when QuickBooks tried to access the company file. Quickbooks Error Code -6150, -1004 Abnormal program termination Runtime Error! Program QBW32.EXE Microsoft Visual C++ Runtime Library Item has missing rows in the item history table Get Decrypted Credit Card Number decryption has failed intuit™ 1-(844) 366 8247 Quickbooks tech support phone number QuickBooks™ phone number(1844)-366-8247) QuickBooks phone number WSA Find all
[Kernel-packages] [Bug 1767396] Re: Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support
** Package changed: linux (Ubuntu) => null-and-void ** Information type changed from Public to Private ** Changed in: null-and-void Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767396 Title: Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support Status in NULL Project: Invalid Bug description: Quickbooks Destop toll free number + 1-844-366-8247 .Quickbooks Errors Support Quickbooks toll free number + 1-844-366-8247 .Quickbooks Errors Support At the time of upgrading QuickBooks to the next version or updating files with information you might encounter messages labeled with error codes, which might interfere with the flow of your work. To resolve 6000, H505, H202, 3371, 6123,1603, 15215 and more critical errors contact our technical experts having extensive knowledge about the software through toll free number + 1-844-366-8247 .Quickbooks Errors Support Common Quickbooks Repairable Problems Error: -6147,0: This is not a QuickBooks data file or there is a problem with the data file Quickbooks Connection has been Lost How to resolve the 'Quickbooks Connection Lost' error message? QuickBooks has Experienced a Problem and Must be Shut Down An error occurred when Quickbooks tried to access the company file. Unrecoverable Error, Quickbooks must shut down Some Sales Orders or Estimates may be incorrectly marked as closed or display incorrect invoiced quantities Quickbooks Rebuild or Verify Errors Error in reload.sql at line xxx Quickbooks Error Code -6000, -82 | 80070057 Quickbooks Error Code -6000,-301: An error occurred when QuickBooks tried to access the company file. Quickbooks Error Code -6150, -1004 Abnormal program termination Runtime Error! Program QBW32.EXE Microsoft Visual C++ Runtime Library Item has missing rows in the item history table Get Decrypted Credit Card Number decryption has failed intuit™ 1-(844) 366 8247 Quickbooks tech support phone number QuickBooks™ phone number(1844)-366-8247) QuickBooks phone number WSA Find all the basic information you need for your Intuit product or service at Intuit Support or call 1(8oo) 366-o992 (QB INTUIT). Quickbooks Phone Number (1844 366-8247), Quickbooks support phone number, Quickbooks support number, Quickbooks tech support number, Quickbooks tech support phone number, Quickbooks technical support number, Quickbooks technical support phone number, Quickbooks customer service phone number, Quickbooks customer support number, Quickbooks customer care number, Quickbooks customer care phone number, Quickbooks customer service phone number, Quickbooks customer service number, Quickbooks help number, Quickbooks help phone number, Quickbooks help desk phone number, Quickbooks help desk number, Quickbooks helpline number, Quickbooks helpline phone number, Quickbooks toll free number, Quickbooks toll free phone number, Quickbooks telephone number, Quickbooks support telephone number, Quickbooks tech support telephone number, Quickbooks technical support telephone number, Quickbooks customer service telephone number, Quickbooks customer care telephone number, Quickbooks help telephone number, Quickbooks 8oo phone number, Quickbooks 8oo number, To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1767396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766445] Re: linux-azure: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- 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/1766445 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid 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-master-bug: 1766441 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767409] [NEW] linux-kvm: -proposed tracker
Public bug reported: 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: 1767397 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.04.23-1 kernel-sru-derivative-of-1767397 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in:
[Kernel-packages] [Bug 1767406] [NEW] linux-azure: -proposed tracker
Public bug reported: 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: 1767397 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: Joshua R. Poulson (jrp) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.04.23-1 kernel-sru-derivative-of-1767397 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) =>
[Kernel-packages] [Bug 1766842] Re: linux: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766842 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767083] Re: linux: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767083 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-lbm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Invalid 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: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766592] Re: linux: 4.13.0-40.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1766592 Title: linux: 4.13.0-40.45 -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: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: 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 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem) derivatives: bug 1766593 (linux-raspi2) kernel-stable-phase-changed:Wednesday, 25. April 2018 08:30 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767403] [NEW] linux-aws: -proposed tracker
Public bug reported: 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: 1767397 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2018.04.23-1 kernel-sru-derivative-of-1767397 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in:
[Kernel-packages] [Bug 1765101] Re: linux: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765101 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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: bug 1765102 (linux-raspi2) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1765101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765018] Re: linux-lts-trusty: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live -- 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/1765018 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Invalid 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: 1765015 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1765018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp