[Kernel-packages] [Bug 1667245] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1655280 *** https://bugs.launchpad.net/bugs/1655280 --- Comment From hbath...@in.ibm.com 2018-04-18 00:21 EDT--- (In reply to comment #16) > The fix mentioned in Launchpad bug 1655280 resolves this issue as well.. Basically, a udev rule file that looks like this: SUBSYSTEM=="memory", ACTION=="online", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="memory", ACTION=="offline", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" put in "/lib/udev/rules.d" dir as part of the kdump-tools package to avoid the need to manually reload kdump.. Thanks Hari -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667245 Title: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- After a memory DLPAR removal, kdump doesn't work: Starting Kernel crash dump capture service... [ 67.714593] kdump-tools[3850]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201702230005/dump-incomplete Copying data : [ 2.1 %] -/usr/sbin/kdump-config: line 639: 3897 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 72.314140] kdump-tools[3850]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad address [ 73.704152] kdump-tools[3850]: * kdump-tools: failed to save vmcore in /var/crash/201702230005 [ 73.823643] kdump-tools[3850]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201702230005/dmesg.201702230005 [ 73.973813] kdump-tools[3850]: The kernel version is not supported. [ 73.974078] kdump-tools[3850]: The makedumpfile operation may be incomplete. [ 73.983506] kdump-tools[3850]: The dmesg log is saved to /var/crash/201702230005/dmesg.201702230005. [ 73.983752] kdump-tools[3850]: makedumpfile Completed. [ 73.983998] kdump-tools[3850]: * kdump-tools: saved dmesg content in /var/crash/201702230005 [ 74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600 [ 74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No such file or directory [ 74.233782] kdump-tools[3850]: Rebooting. [ 86.629777] reboot: Restarting system The kdump service should be restarted after the memory DLPAR operation. C ---uname output--- Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. do a memory DLPAR removal operation 3. trigger kdump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1667245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1667245] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1655280 *** https://bugs.launchpad.net/bugs/1655280 --- Comment From hbath...@in.ibm.com 2018-04-18 00:16 EDT--- The fix mentioned in Launchpad bug 1655280 resolves this issue as well.. Thanks Hari -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667245 Title: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- After a memory DLPAR removal, kdump doesn't work: Starting Kernel crash dump capture service... [ 67.714593] kdump-tools[3850]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201702230005/dump-incomplete Copying data : [ 2.1 %] -/usr/sbin/kdump-config: line 639: 3897 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 72.314140] kdump-tools[3850]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad address [ 73.704152] kdump-tools[3850]: * kdump-tools: failed to save vmcore in /var/crash/201702230005 [ 73.823643] kdump-tools[3850]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201702230005/dmesg.201702230005 [ 73.973813] kdump-tools[3850]: The kernel version is not supported. [ 73.974078] kdump-tools[3850]: The makedumpfile operation may be incomplete. [ 73.983506] kdump-tools[3850]: The dmesg log is saved to /var/crash/201702230005/dmesg.201702230005. [ 73.983752] kdump-tools[3850]: makedumpfile Completed. [ 73.983998] kdump-tools[3850]: * kdump-tools: saved dmesg content in /var/crash/201702230005 [ 74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600 [ 74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No such file or directory [ 74.233782] kdump-tools[3850]: Rebooting. [ 86.629777] reboot: Restarting system The kdump service should be restarted after the memory DLPAR operation. C ---uname output--- Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. do a memory DLPAR removal operation 3. trigger kdump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1667245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748520] Re: SDXC card reader not recognized
[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/1748520 Title: SDXC card reader not recognized Status in linux package in Ubuntu: Expired Bug description: On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot is non-responsive. uname -a Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Installing sdhci and sdhci-pci modules (with or without adding a /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not work. After a reboot, the drivers are not installed. A device /dev/mmcblk0 is missing. This used to be different in previous kernels 4.13... (although I have no record when last I tested). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-33-generic 4.13.0-33.36 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1055 F pulseaudio wolf 1399 F pulseaudio /dev/snd/controlC0: gdm1055 F pulseaudio wolf 1399 F pulseaudio Date: Fri Feb 9 20:25:21 2018 HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4 InstallationDate: Installed on 2017-10-20 (112 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-33-generic N/A linux-backports-modules-4.13.0-33-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748520/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739073] Re: 'Synaptics Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo Thinkpad x120e AE' suddenly
[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/1739073 Title: 'Synaptics Touchpad' incorrectly detected as PS/2 mouse in 'Lenovo Thinkpad x120e AE' suddenly Status in linux package in Ubuntu: Expired Bug description: 1.Laptop model: LENOVO Thinkpad x120e 0611-AE5 2.Manufacturer of the Touchpad: Synaptics 3.When the symptom first appeared: around 3 month ago (August 2017) I first encountered this issue after dual boot Linux Ubuntu-MATE 16.04 LTS and Windows 10. My system always update. Touchpad suddenly not working when the laptop woke up from sleep in Windows 10 OS. Tried to add parameters in GRUB: quiet splash i8042.reset i8042.nomux=1 i8042.nopnp=1 i8042.noloop=1 without any positive result (touchpad still not working), but, now xinput detect PS/2 Generic Mouse for touchpad (before touchpad is not detected at all). Attached dmesg and devices file. Thanks. Regards, ariefcfa --- ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mariefhidayat 1471 F pulseaudio /dev/snd/controlC0: mariefhidayat 1471 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.3 InstallationDate: Installed on 2017-12-15 (4 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: LENOVO 0611AE5 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=1c01f4dc-5d5e-48d7-b66f-dd8e5b84060a ro quiet splash i8042.reset i8042.nomux=1 i8042.nopnp=1 i8042.noloop=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-38-generic N/A linux-backports-modules-4.10.0-38-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.10.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8FET33WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 0611AE5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8FET33WW(1.17):bd11/07/2012:svnLENOVO:pn0611AE5:pvrThinkPadX120e:rvnLENOVO:rn0611AE5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 0611AE5 dmi.product.version: ThinkPad X120e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749401] Re: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: package linux-image-4.4.0-83-generic is not ready for configuration cannot configure (c
[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/1749401 Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: package linux-image-4.4.0-83-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Expired Bug description: My computer failed to boot correctly a few weeks ago, and after restarting several times with no success, I booted with a previous line on the menu that comes up. That seemed to work, but now there are further problems. I'm afraid I am not very tech-savvy, as you can probably tell. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-83-generic 4.4.0-83.106 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marilyn1628 F pulseaudio Date: Wed Feb 14 09:13:16 2018 DuplicateSignature: package:linux-image-4.4.0-83-generic:4.4.0-83.106 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package linux-image-4.4.0-83-generic (--configure): package linux-image-4.4.0-83-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-83-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=4789a4e3-ea9b-4a41-b54d-bb38c94dbe83 InstallationDate: Installed on 2016-05-15 (639 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Acer Aspire 5735 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=2b4b8588-9bb8-4846-a576-3c3c4db4a618 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: grub-pc 2.02~beta2-36ubuntu3.16 SourcePackage: linux Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: package linux-image-4.4.0-83-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.07 dmi.board.name: CathedralPeak dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.07:bd08/27/2008:svnAcer:pnAspire5735:pvr0100:rvnAcer:rnCathedralPeak:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5735 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
Right, I wasn't give it too much hoping. I'll escalate the issue to UVC upstream to let them know the issue. I'll also ask Realtek if there's a way (maybe via USB control message) to switch between UVC1.0/UVC1.5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2
I guess you can avoid the issue by using kernel parameter "nomodeset" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758496 Title: Backlight does not work on a MacBookAir3,2 Status in linux package in Ubuntu: Incomplete Bug description: Backlight control does not work and there are no entries in /sys/class/backlight. When I boot my system with the option GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the brightness with the command xrandr on a terminal. I attach all the system information about this problem. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 07:22:05 2018 InstallationDate: Installed on 2018-03-04 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookAir3,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor 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: 11/18/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B01.1011181342 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942C5DF58193131B dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir3,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942C5DF58193131B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B: dmi.product.family: MacBook dmi.product.name: MacBookAir3,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764917] [NEW] Network Manager fails to appear: unable to access wifi networks
Public bug reported: The network discovery functions does not appear on the main bar in the upper right hand corner. I am only provided with ethernet and VPN options. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 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.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 17 19:04:11 2018 InstallationDate: Installed on 2018-04-18 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1764917 Title: Network Manager fails to appear: unable to access wifi networks Status in bcmwl package in Ubuntu: New Bug description: The network discovery functions does not appear on the main bar in the upper right hand corner. I am only provided with ethernet and VPN options. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 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.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 17 19:04:11 2018 InstallationDate: Installed on 2018-04-18 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1764917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] [NEW] e1000e msix interrupts broken in linux-image-4.15.0-15-generic
Public bug reported: 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764892 Title: e1000e msix interrupts broken in linux-image-4.15.0-15-generic Status in linux package in Ubuntu: New 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] 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 1764892 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/1764892 Title: e1000e msix interrupts broken in linux-image-4.15.0-15-generic Status in linux package in Ubuntu: Incomplete 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Attachment added: "sos report for 16.04.04 with 4.15 kernel tesing (no screen blur after enable x-window)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5120260/+files/sosreport-2288Hv5uefi16.04.44.15-20180417120113.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu20 --- zfs-linux (0.6.5.6-0ubuntu20) xenial; urgency=medium * Fix mmap'd libaio read on non-prefaulted page deadlock (LP: #1754584) - Revert previous fix as there still is a potential for deadlock on the prefaulted page(s). Resolve the issue by only taking a reference on the page when copying it and not the page lock. The inode range lock protects against concurrent updates via zfs_read() and zfs_write(). -- Colin Ian KingWed, 28 Mar 2018 14:35:11 +0100 ** Changed in: zfs-linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 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 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Attachment added: "Test matrix for sceen blur on 16.04.4 with 4.4 4.13 4.15 kernel and 18.04" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5120230/+files/test-matrix-on-1604-1804.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754584] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 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 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0:
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
This bug was fixed in the package zfs-linux - 0.6.5.11-1ubuntu3.3 --- zfs-linux (0.6.5.11-1ubuntu3.3) artful; urgency=medium * Fix mmap'd libaio read on non-prefaulted page deadlock (LP: #1754584) - Revert previous fix as there still is a potential for deadlock on the prefaulted page(s). Resolve the issue by only taking a reference on the page when copying it and not the page lock. The inode range lock protects against concurrent updates via zfs_read() and zfs_write(). -- Colin Ian KingWed, 28 Mar 2018 08:56:18 +0100 ** Changed in: zfs-linux (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 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 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd
[Kernel-packages] [Bug 1764892] Re: e1000e msix interrupts broken in linux-image-4.15.0-15-generic
** 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/1764892 Title: e1000e msix interrupts broken in linux-image-4.15.0-15-generic Status in linux package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568341] Re: Boot hangs at: /scripts/local-premount/uswsusp
Appears to be a "thing" with Toshiba laptops. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568341 Title: Boot hangs at: /scripts/local-premount/uswsusp Status in linux package in Ubuntu: Confirmed Bug description: When booting Ubuntu kernels 4.4.0-16 through 4.4.0-18 (either by default or upstart), it hangs during boot noting as per the attached screenshot: Begin: Running /scripts/local-premount ... With debug=y kernel parameter it hangs at: /scripts/local-premount/uswsusp This doesn't happen via 4.4.0-15. Git bisect revealed: # first bad commit: [746a312bf960810a7ccfb16eefeec68a335392b4] UBUNTU: Start new release WORKAROUND: Uninstall package: uswsusp --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moniker1927 F pulseaudio /dev/snd/controlC1: moniker1927 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c099059e-62ee-4a3a-8dc7-64bf4eb0c960 InstallationDate: Installed on 2015-12-18 (112 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: TOSHIBA Satellite S55-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-01-20 (80 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.10 dmi.board.name: 06F1 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr5.10:bd10/14/2015:svnTOSHIBA:pnSatelliteS55-C:pvrPSPTJU-006005:rvnFF50:rn06F1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite S55-C dmi.product.version: PSPTJU-006005 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568341] Re: Boot hangs at: /scripts/local-premount/uswsusp
** Changed in: linux (Ubuntu) Status: Invalid => 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/1568341 Title: Boot hangs at: /scripts/local-premount/uswsusp Status in linux package in Ubuntu: Confirmed Bug description: When booting Ubuntu kernels 4.4.0-16 through 4.4.0-18 (either by default or upstart), it hangs during boot noting as per the attached screenshot: Begin: Running /scripts/local-premount ... With debug=y kernel parameter it hangs at: /scripts/local-premount/uswsusp This doesn't happen via 4.4.0-15. Git bisect revealed: # first bad commit: [746a312bf960810a7ccfb16eefeec68a335392b4] UBUNTU: Start new release WORKAROUND: Uninstall package: uswsusp --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moniker1927 F pulseaudio /dev/snd/controlC1: moniker1927 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=c099059e-62ee-4a3a-8dc7-64bf4eb0c960 InstallationDate: Installed on 2015-12-18 (112 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: TOSHIBA Satellite S55-C Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic root=/dev/mapper/ubuntu--vg-root ro ipv6.disable=1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 Tags: xenial Uname: Linux 4.4.0-15-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-01-20 (80 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.10 dmi.board.name: 06F1 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr5.10:bd10/14/2015:svnTOSHIBA:pnSatelliteS55-C:pvrPSPTJU-006005:rvnFF50:rn06F1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite S55-C dmi.product.version: PSPTJU-006005 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755073] Re: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64
-- before proposed -- Ubuntu 17.10 (GNU/Linux 4.13.0-38-generic aarch64) ubuntu@anuchin:~$ sudo bash root@anuchin:~# modprobe zram root@anuchin:~# echo 1 > /sys/block/zram0/reset root@anuchin:~# echo deflate > /sys/block/zram0/comp_algorithm root@anuchin:~# echo 128M > /sys/block/zram0/disksize root@anuchin:~# mkfs.ext4 -F /dev/zram0 mke2fs 1.43.5 (04-Aug-2017) Discarding device blocks: done Creating filesystem with 32768 4k blocks and 32768 inodes Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: manjo@lazy:~$ ipmitool -H 10.229.48.14 -I lanplus -U admin -P admin sol activate [SOL Session operational. Use ~? for help] [ 1420.012055] watchdog: BUG: soft lockup - CPU#14 stuck for 22s! [mkfs.ext4:3121] [ 1424.023938] watchdog: BUG: soft lockup - CPU#40 stuck for 23s! [kworker/u96:2:406] [ 1454.099071] INFO: rcu_sched self-detected stall on CPU [ 1454.104260] 14-...: (14998 ticks this GP) idle=796/141/0 softirq=4896/4896 fqs=7500 [ 1454.107070] INFO: rcu_sched detected stalls on CPUs/tasks: [ 1454.107076] 14-...: (14998 ticks this GP) idle=796/141/0 softirq=4896/4896 fqs=7500 [ 1454.107077] (detected by 40, t=15002 jiffies, g=3929, c=3928, q=4597) [ 1454.134272] (t=15008 jiffies g=3929 c=3928 q=4597) -- after proposed -- ubuntu@anuchin:~$ uname -a Linux anuchin 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:20:13 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@anuchin:~$ sudo bash root@anuchin:~# modprobe zram root@anuchin:~# echo 1 > /sys/block/zram0/reset root@anuchin:~# echo deflate > /sys/block/zram0/comp_algorithm root@anuchin:~# echo 128M > /sys/block/zram0/disksize root@anuchin:~# mkfs.ext4 -F /dev/zram0 mke2fs 1.43.5 (04-Aug-2017) Discarding device blocks: done Creating filesystem with 32768 4k blocks and 32768 inodes Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done root@anuchin:~# ** 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/1755073 Title: ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64 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: == SRU Justification == Enabling virtual mapped kernel stacks breaks the thunderx_zip driver. On compression or decompression the executing CPU hangs in an endless loop. The reason for this is the usage of __pa() by the driver that does not work for an address that is not part of the 1:1 mapping. == Fix == The patch in comment #12 fixes it. To reproduce the bug (and test the new kernel), see comment #9. == Regression Potential == The patch affects only the thunderx_zip driver (that is already in a completely broken state), so the regression potential is low. --- This is a POTENTIAL REGRESSION. This test has passed with 4.13.0-36.40, but not 4.13.0-37.42 The test will stuck with error message in dmesg: ubuntu@starmie-kernel:~$ dmesg [ 470.227210] zram: Added device: zram0 [ 472.262544] zram0: detected capacity change from 0 to 134217728 [ 472.396960] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 475.761947] zram0: detected capacity change from 134217728 to 0 [ 476.796641] zram0: detected capacity change from 0 to 134217728 [ 476.909118] EXT4-fs (zram0): mounted filesystem with ordered data mode. Opts: (null) [ 480.233817] zram0: detected capacity change from 134217728 to 0 [ 481.239001] zram0: detected capacity change from 0 to 134217728 [ 508.079684] watchdog: BUG: soft lockup - CPU#8 stuck for 23s! [mkfs.ext4:2253] [ 508.086994] Modules linked in: lz4 lz4_compress zram nls_iso8859_1 thunderx_edac i2c_thunderx thunderx_zip i2c_smbus shpchp cavium_rng_vf cavium_rng gpio_keys ipmi_ssif uio_pdrv_genirq uio ipmi_devintf ipmi_msghandler ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce drm ghash_ce sha2_ce sha1_ce ahci libahci thunder_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs aes_neon_blk crypto_simd cryptd [ 508.087138] CPU: 8
[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU
A Xenial test kernel is now also available. Xenial required commit 70b8301f6 as a prerequisite. The xenial test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1747134/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/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in intel: New 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: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1747134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762913] Re: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock)
I removed the Artful bug task per comment #4. ** No longer affects: linux (Ubuntu 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/1762913 Title: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Application Cdeadmin- 2018-04-03 05:20:56 == == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 == --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT --- The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of commits need to be backported as suggested by Nick piggin. == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 == which is >>> From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001 From: Nicholas Piggin Date: Wed, 17 Jan 2018 22:47:22 +1000 Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace The powerpc NMI IPIs may not be recoverable if they are taken in some sections of code, and also there have been and still are issues with taking NMIs (in KVM guest code, in firmware, etc) which makes them a bit dangerous to use. Generic code like softlockup detector and rcu stall detectors really hammer on trigger_*_backtrace, which has lead to further problems because we've implemented it with the NMI. So stop providing NMI backtraces for now. Importantly, the powerpc code uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the softlockup and rcu hang detection traces are not being printed because the CPU is stuck with interrupts off, then the hard lockup watchdog should get it with the NMI IPI. Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup watchdog") Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman --- arch/powerpc/include/asm/nmi.h | 4 arch/powerpc/kernel/watchdog.c | 22 -- 2 files changed, 26 deletions(-) diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h index e97f586..9c80939 100644 --- a/arch/powerpc/include/asm/nmi.h +++ b/arch/powerpc/include/asm/nmi.h @@ -4,10 +4,6 @@ #ifdef CONFIG_PPC_WATCHDOG extern void arch_touch_nmi_watchdog(void); -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask, -bool exclude_self); -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace - #else static inline void arch_touch_nmi_watchdog(void) {} #endif diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c index 87da80c..3963baa 100644 --- a/arch/powerpc/kernel/watchdog.c +++ b/arch/powerpc/kernel/watchdog.c @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void) } return 0; } - -static void handle_backtrace_ipi(struct pt_regs *regs) -{ - nmi_cpu_backtrace(regs); -} - -static void raise_backtrace_ipi(cpumask_t *mask) -{ - unsigned int cpu; - - for_each_cpu(cpu, mask) { - if (cpu == smp_processor_id()) - handle_backtrace_ipi(NULL); - else - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100); - } -} - -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self) -{ - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi); -} -- 2.7.4 >>> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764866] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764866 Title: [123779.594327] general protection fault: [#1] SMP PTI Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 beta, clean install, updates twice a day. Loaded updates this afternoon, no reboot required. Closed the laptop, went home and opened it. Some issues winth networking so decided te restart. That didn't finish well so had to force a power cycle. Booted well, but got this error report. Machine is a Dell Latitude 3540 (early 2014). If you need more information just let me know. cheers Tom ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1184 F pulseaudio thomas 1495 F pulseaudio Date: Tue Apr 17 18:41:18 2018 Failure: oops HibernationDevice: RESUME=UUID=8be4eddb-bbc0-427f-89b0-35a54564b33a InstallationDate: Installed on 2018-04-14 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407) MachineType: Dell Inc. Latitude 3540 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: [123779.594327] general protection fault: [#1] SMP PTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 02RKKX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/17/2014:svnDellInc.:pnLatitude3540:pvrA06:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Latitude 3540 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764866] [NEW] [123779.594327] general protection fault: 0000 [#1] SMP PTI
Public bug reported: Ubuntu 18.04 beta, clean install, updates twice a day. Loaded updates this afternoon, no reboot required. Closed the laptop, went home and opened it. Some issues winth networking so decided te restart. That didn't finish well so had to force a power cycle. Booted well, but got this error report. Machine is a Dell Latitude 3540 (early 2014). If you need more information just let me know. cheers Tom ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1184 F pulseaudio thomas 1495 F pulseaudio Date: Tue Apr 17 18:41:18 2018 Failure: oops HibernationDevice: RESUME=UUID=8be4eddb-bbc0-427f-89b0-35a54564b33a InstallationDate: Installed on 2018-04-14 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407) MachineType: Dell Inc. Latitude 3540 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: [123779.594327] general protection fault: [#1] SMP PTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 02RKKX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/17/2014:svnDellInc.:pnLatitude3540:pvrA06:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Latitude 3540 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764866 Title: [123779.594327] general protection fault: [#1] SMP PTI Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 beta, clean install, updates twice a day. Loaded updates this afternoon, no reboot required. Closed the laptop, went home and opened it. Some issues winth networking so decided te restart. That didn't finish well so had to force a power cycle. Booted well, but got this error report. Machine is a Dell Latitude 3540 (early 2014). If you need more information just let me know. cheers Tom ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1184 F pulseaudio thomas 1495 F pulseaudio Date: Tue Apr 17 18:41:18 2018 Failure: oops HibernationDevice: RESUME=UUID=8be4eddb-bbc0-427f-89b0-35a54564b33a InstallationDate: Installed on 2018-04-14 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407) MachineType: Dell Inc. Latitude 3540 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: [123779.594327] general protection fault: [#1] SMP PTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 02RKKX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/17/2014:svnDellInc.:pnLatitude3540:pvrA06:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Latitude 3540 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1764859] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764859 Title: BUG: scheduling while atomic: Media/11726/0x0002 Status in linux package in Ubuntu: Confirmed Bug description: - ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Tue Apr 17 22:12:39 2018 Failure: oops HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb InstallationDate: Installed on 2018-03-02 (46 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: Media/11726/0x0002 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764859] [NEW] BUG: scheduling while atomic: Media/11726/0x00000002
Public bug reported: - ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Tue Apr 17 22:12:39 2018 Failure: oops HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb InstallationDate: Installed on 2018-03-02 (46 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: Media/11726/0x0002 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764859 Title: BUG: scheduling while atomic: Media/11726/0x0002 Status in linux package in Ubuntu: Confirmed Bug description: - ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Tue Apr 17 22:12:39 2018 Failure: oops HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb InstallationDate: Installed on 2018-03-02 (46 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: Media/11726/0x0002 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755595] Re: sbsa watchdog crashes thunderx2 system
Tested the -proposed kernel on boomer with 6.2 fw version. ubuntu@boomer:~$ dmesg | grep sbsa ubuntu@boomer:~$ sudo modprobe sbsa_gwdt ubuntu@boomer:~$ dmesg | grep sbsa ubuntu@boomer:~$ lsmod | grep sbsa sbsa_gwdt 16384 0 ubuntu@boomer:~$ ls /dev/watchdog ls: cannot access '/dev/watchdog': No such file or directory ubuntu@boomer:~$ Looks like sbsa is not exposed by fw6.2 on this thunderx2 system. No kernel crash was observed. ** 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/1755595 Title: sbsa watchdog crashes thunderx2 system 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] Using the SBSA watchdog will crash the OS on ThunderX2 systems. This is not an issue in current firmware because the SBSA watchdog is not exposed - but it is likely to be introduced in a future update. [Test Case] $ sudo bash # cat < /dev/watchdog [Regression Risk] The fix is restricted the sbsa_gwdt driver, which is only currently available on some arm64 servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764816] Re: drivers/gpu/drm/bridge/adv7511/adv7511.ko missing
** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: Won't Fix => 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/1764816 Title: drivers/gpu/drm/bridge/adv7511/adv7511.ko missing Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: This driver has the same module name as another module. Only one ends up getting installed, and the missing one causes the display and audio to fail to work with our snapdragon kernel. Fix: Sauce patch to rename the drm driver to adv7511_drm.ko. Will pursue a more permanent fix upstream, but we need a fix in place now for the release. Test Case: Do a build and confirm both modules are now present. Regression Potential: Could cause problems if anyone is using the module name in scripts or blacklisting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This file is one with the failed boot, unfortunately the kernel panic message don't appear. Unlike the other file with the failure I uploaded before, on this one the boot failed. I was helped on #ubuntu+1 on how to add netconsole to initramfs, so I was able to obtain the first 7 seconds of the log. ** Attachment added: "netconsole15.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119900/+files/netconsole15.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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias:
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** No longer affects: install-package (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/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762913] Comment bridged from LTC Bugzilla
--- Comment From ppaid...@in.ibm.com 2018-04-17 15:21 EDT--- (In reply to comment #9) > The Bionic request has been sent. However, because Artful is a stable > release, it requires testing before submitting a SRU request. > > I built an Artful test kernel with commit > 47712a921bb781caf69fca9eae43be19968816cb. The test kernel can be downloaded > from: > http://kernel.ubuntu.com/~jsalisbury/lp1762913 > > Can you test this kernel and see if it resolves this bug? > > Note, to test this kernel, you need to install both the linux-image and > linux-image-extra .deb packages. > > Thanks in advance! Hi I have tested the above artful test kernel, which works fine. But developer mentioned the fixes really needs in 4.15 bionic kernel(where it has support to send NMI IPI's which causes this bug - r13 clobber bug). In 4.13 kernel there is no support for that, hence those fixes will not have any impact. Thanks Pridhiviraj -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762913 Title: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Application Cdeadmin- 2018-04-03 05:20:56 == == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 == --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT --- The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of commits need to be backported as suggested by Nick piggin. == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 == which is >>> From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001 From: Nicholas Piggin Date: Wed, 17 Jan 2018 22:47:22 +1000 Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace The powerpc NMI IPIs may not be recoverable if they are taken in some sections of code, and also there have been and still are issues with taking NMIs (in KVM guest code, in firmware, etc) which makes them a bit dangerous to use. Generic code like softlockup detector and rcu stall detectors really hammer on trigger_*_backtrace, which has lead to further problems because we've implemented it with the NMI. So stop providing NMI backtraces for now. Importantly, the powerpc code uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the softlockup and rcu hang detection traces are not being printed because the CPU is stuck with interrupts off, then the hard lockup watchdog should get it with the NMI IPI. Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup watchdog") Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman --- arch/powerpc/include/asm/nmi.h | 4 arch/powerpc/kernel/watchdog.c | 22 -- 2 files changed, 26 deletions(-) diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h index e97f586..9c80939 100644 --- a/arch/powerpc/include/asm/nmi.h +++ b/arch/powerpc/include/asm/nmi.h @@ -4,10 +4,6 @@ #ifdef CONFIG_PPC_WATCHDOG extern void arch_touch_nmi_watchdog(void); -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask, -bool exclude_self); -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace - #else static inline void arch_touch_nmi_watchdog(void) {} #endif diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c index 87da80c..3963baa 100644 --- a/arch/powerpc/kernel/watchdog.c +++ b/arch/powerpc/kernel/watchdog.c @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void) } return 0; } - -static void handle_backtrace_ipi(struct pt_regs *regs) -{ - nmi_cpu_backtrace(regs); -} - -static void raise_backtrace_ipi(cpumask_t *mask) -{ - unsigned int cpu; - - for_each_cpu(cpu, mask) { - if (cpu == smp_processor_id()) - handle_backtrace_ipi(NULL); - else - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100); - } -} - -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self) -{ - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi); -} -- 2.7.4 >>> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
** Attachment added: "dmesg_ok.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119845/+files/dmesg_ok.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
Many tries were required until I could obtain a useful log. As it can be seen in the kernel command line, I had to add many debug options to obtain this. ** Attachment added: "dmesg_falha.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+attachment/5119844/+files/dmesg_falha.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. 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 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias:
[Kernel-packages] [Bug 1764816] [NEW] drivers/gpu/drm/bridge/adv7511/adv7511.ko missing
Public bug reported: SRU Justification Impact: This driver has the same module name as another module. Only one ends up getting installed, and the missing one causes the display and audio to fail to work with our snapdragon kernel. Fix: Sauce patch to rename the drm driver to adv7511_drm.ko. Will pursue a more permanent fix upstream, but we need a fix in place now for the release. Test Case: Do a build and confirm both modules are now present. Regression Potential: Could cause problems if anyone is using the module name in scripts or blacklisting the module. ** Affects: linux (Ubuntu) Importance: Critical Assignee: Seth Forshee (sforshee) 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/1764816 Title: drivers/gpu/drm/bridge/adv7511/adv7511.ko missing Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: This driver has the same module name as another module. Only one ends up getting installed, and the missing one causes the display and audio to fail to work with our snapdragon kernel. Fix: Sauce patch to rename the drm driver to adv7511_drm.ko. Will pursue a more permanent fix upstream, but we need a fix in place now for the release. Test Case: Do a build and confirm both modules are now present. Regression Potential: Could cause problems if anyone is using the module name in scripts or blacklisting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Description changed: + == 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. -- You 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: In Progress 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 1761729] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-04-17 13:13 EDT--- The logs show some "read_all" process - presumably part of the test suite - that is trying to read kernel text memory (via /dev/mem) and triggering the BUG. Not clear if the attempt should have been failed gracefully or not. I'd assume the expectation is that a illegal read from /dev/mem should return an error rather than panic. Comment #21 shows a different panic, and since no logs or vmcore are provided I can't tell any more about it. If this latest panic is the only reason the bug is open, we need to move that to a new bugzilla as it is not the same issue. --- Comment From dougm...@us.ibm.com 2018-04-17 13:15 EDT--- Comment #19 also shows a different issue than originally reported. So, it seems this bugzilla has deviated from the original 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/1761729 Title: Ubuntu 18.04 Machine crashed while running ltp. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Briggs P8 ]: Machine crashed while running ltp. ---Environment-- Kernel Build: Ubuntu 18.04 System Name : ltc-briggs2 Model/Type : P8 Platform: BML ---Uname output--- root@ltc-briggs2:~# uname -a Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Steps to reproduce-- $ git clone https://github.com/linux-test-project/ltp.git $ cd ltp $ make autotools $ ./configure $ make $ make install ltp = root@ltc-briggs2:~# root@ltc-briggs2:~# [10781.098337] LTP: starting fs_inod01 (fs_inod $TMPDIR 10 10 10) [10782.837910] LTP: starting linker01 (linktest.sh 1000 1000) [10784.504474] LTP: starting openfile01 (openfile -f10 -t10) [10784.534953] LTP: starting inode01 [10784.550767] LTP: starting inode02 [10784.739104] LTP: starting stream01 [10784.740840] LTP: starting stream02 [10784.742487] LTP: starting stream03 [10784.744532] LTP: starting stream04 [10784.746087] LTP: starting stream05 [10784.747722] LTP: starting ftest01 [10785.142054] LTP: starting ftest02 [10785.158852] LTP: starting ftest03 [10785.404760] LTP: starting ftest04 [10785.527197] LTP: starting ftest05 [10785.937164] LTP: starting ftest06 [10785.958360] LTP: starting ftest07 [10786.463382] LTP: starting ftest08 [10786.592998] LTP: starting lftest01 (lftest 100) [10786.672707] LTP: starting writetest01 (writetest) [10786.774292] LTP: starting fs_di (fs_di -d $TMPDIR) [10792.973510] LTP: starting proc01 (proc01 -m 128) [10793.865686] ICMPv6: process `proc01' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead [10795.785593] LTP: starting read_all_dev (read_all -d /dev -e '/dev/watchdog?(0)' -q -r 10) [10795.895774] NET: Registered protocol family 40 [10795.918763] Bluetooth: Core ver 2.22 [10795.918866] NET: Registered protocol family 31 [10795.918909] Bluetooth: HCI device and connection manager initialized [10795.918955] Bluetooth: HCI socket layer initialized [10795.918991] Bluetooth: L2CAP socket layer initialized [10795.919032] Bluetooth: SCO socket layer initialized [10798.374850] usercopy: kernel memory exposure attempt detected from 29431ea4 () (1023 bytes) [10798.374952] [ cut here ] [10798.374988] kernel BUG at /build/linux-2BXDjB/linux-4.15.0/mm/usercopy.c:72! [10798.375041] Oops: Exception in kernel mode, sig: 5 [#1] [10798.375080] LE SMP NR_CPUS=2048 [10871.343999650,5] OPAL: Switch to big-endian OS NUMA PowerNV [10798.375117] [10876.190849323,5] OPAL: Switch to little-endian OS Modules linked in: hci_vhci bluetooth ecdh_generic vhost_vsock cuse vmw_vsock_virtio_transport_common userio vsock uhid vhost_net vhost tap snd_seq snd_seq_device snd_timer snd soundcore binfmt_misc sctp quota_v2 quota_tree nls_iso8859_1 ntfs xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter kvm_hv kvm idt_89hpesx vmx_crypto ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd at24 powernv_rng joydev input_leds mac_hid uio_pdrv_genirq uio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss iw_cm nfs_acl lockd ib_cm grace iscsi_tcp [10798.375636] libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq
[Kernel-packages] [Bug 1764807] [NEW] [wishlist] please add zfsutils-linux to the seed(s)
Public bug reported: For those using ZFS, it would sometimes be handy to have all the tooling available in the live environment. Currently, the live environment only has the kernel module which is unfortunately not enough to interact with this filesystem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu20 ProcVersionSignature: Ubuntu 4.4.0-120.144-generic 4.4.117 Uname: Linux 4.4.0-120-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 17 13:05:00 2018 InstallationDate: Installed on 2016-12-06 (496 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764807 Title: [wishlist] please add zfsutils-linux to the seed(s) Status in zfs-linux package in Ubuntu: New Bug description: For those using ZFS, it would sometimes be handy to have all the tooling available in the live environment. Currently, the live environment only has the kernel module which is unfortunately not enough to interact with this filesystem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu20 ProcVersionSignature: Ubuntu 4.4.0-120.144-generic 4.4.117 Uname: Linux 4.4.0-120-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 17 13:05:00 2018 InstallationDate: Installed on 2016-12-06 (496 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1764807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints
Retpoline files for Trusty kernel 3.13.0-145-generic are being generated as expected. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758856 Title: retpoline hints: primary infrastructure and initial hints 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: Tracking bug for the application of the retpoline hint tracking support. We are having terrible trouble with hints changing on every build. Upstream is moving to hinting those indirections which have been reviewed and are good. This includes direct hinting of PVOPS and the like which are the ones which change all the time as new ones appear and dissappear. Backport the hint support and add our own bespoke checkers against this data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints
Retpoline files for Artful kernel 4.13.0-39-generic are being generated as expected. ** 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/1758856 Title: retpoline hints: primary infrastructure and initial hints 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: Tracking bug for the application of the retpoline hint tracking support. We are having terrible trouble with hints changing on every build. Upstream is moving to hinting those indirections which have been reviewed and are good. This includes direct hinting of PVOPS and the like which are the ones which change all the time as new ones appear and dissappear. Backport the hint support and add our own bespoke checkers against this data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758856] Re: retpoline hints: primary infrastructure and initial hints
Retpoline files for Xenial kernel 4.4.0-121-generic are being generated as expected. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758856 Title: retpoline hints: primary infrastructure and initial hints 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: Tracking bug for the application of the retpoline hint tracking support. We are having terrible trouble with hints changing on every build. Upstream is moving to hinting those indirections which have been reviewed and are good. This includes direct hinting of PVOPS and the like which are the ones which change all the time as new ones appear and dissappear. Backport the hint support and add our own bespoke checkers against this data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel
Confirmed dkms builds are successful with Xenial kernel 4.4.0-121-generic (tested with fwts-efi-runtime-dkms). ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760876 Title: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: Was installing the kernel 4.15.0-14-generic when that crash happened. Now libelf-dev is requested and need to be added as a dependency. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: r8168 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.15.0-14-generic Date: Tue Apr 3 15:39:06 2018 PackageVersion: 18.03.00-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: fwts Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729085] Re: [18.04] Missing vNIC module in the installer
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729085 Title: [18.04] Missing vNIC module in the installer Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Mirroring over for 18.04 installer. Canonical: Please add the ibmvnic module to the installer for 18.04. Thank you. == Comment: #0 - YUECHANG E. MEI - 2017-02-27 11:33:10 == ---Problem Description--- We tried to install ubuntu 16.04.2 by using vNIC. When we tried to load the installer, we saw an issue. Comment from bug 144675, it looks like the ibmvnic module is not included in 16.04.2 or 17.04 installer. GNU GRUB version 2.02~beta2-vlan1 ++ | Install Ubuntu 17.04 GA w/ multipath and preseed | | Install Ubuntu 17.04 GA w/ multipath | | Install Ubuntu 17.04 GA w/ preseed | |*Install Ubuntu Yakkety (16.10 development) | | Install Ubuntu Yakkety (16.10 w/ multipath) | | Install Ubuntu 16.04 GA | | Install Ubuntu 16.04 GA w/ multipath | | Install Ubuntu 16.04 GA w/ preseed | | Install Ubuntu 16.04 GA w/ multipath and preseed | | Install Ubuntu 14.04.4 LTS | | Install Ubuntu 14.04.5 LTS | | Rescue mode | ++ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. ?? [!!] Download debconf preconfiguration file ?? ? ? ? Failed to retrieve the preconfiguration file ? ? The file needed for preconfiguration could not be retrieved from ? ? http://10.33.11.31/distros/ubuntu/preseed.cfg. The installation will ? ? proceed in non-automated mode.? ? ? ? ? ? ? ? but then we cannot go any further...drop to the shell and we do not see any ibmvnic loaded, try to load it is not found. ~ # lsmod|grep ibm ibmveth31190 0 ~ # modprobe ibmvnic modprobe: FATAL: Module ibmvnic not found in directory /lib/modules/4.4.0-21-generic ~ # ---boot type--- Network boot ---bootloader--- grub ---Point of failure--- Failed during boot of installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1729085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel
Confirmed dkms builds are successful with Artful kernel 4.13.0-39-generic (tested with fwts-efi-runtime-dkms). ** 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/1760876 Title: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: Was installing the kernel 4.15.0-14-generic when that crash happened. Now libelf-dev is requested and need to be added as a dependency. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: r8168 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.15.0-14-generic Date: Tue Apr 3 15:39:06 2018 PackageVersion: 18.03.00-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: fwts Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764792] 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 1764792 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/1764792 Title: Build Nvidia drivers in conjunction with kernel Status in linux package in Ubuntu: Incomplete Bug description: We want to deliver a great out of the box experience of Ubuntu users running on Nvidia GPU enabled platforms (including instances in the cloud). Can we explore the possibility of pre-building the nvidia drivers alongside the kernel build, but not pre-link the drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel
Confirmed dkms builds are successful with Trusty kernel 3.13.0-145-generic (tested with fwts-efi-runtime-dkms). ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760876 Title: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Bug description: Was installing the kernel 4.15.0-14-generic when that crash happened. Now libelf-dev is requested and need to be added as a dependency. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: r8168 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.15.0-14-generic Date: Tue Apr 3 15:39:06 2018 PackageVersion: 18.03.00-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: fwts Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]
It sounds like the root cause of this bug, then, is that the ipr driver is taking longer than normal / longer than reasonable to initialize+scan. If this is a regression vs. previous Ubuntu releases (as opposed to, say, an instance of failing hardware on a particular test machine), then we need to be looking at a kernel bug; opening a task on the linux package for this. Separately, based on the investigation and findings up to this point, I think d-i should also be fixed to scan disks synchronously, because there is certainly a race here; and given the design of d-i, which does not automatically update the UI with details of late-detected disks, I think it's more important to be reliable than fast. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based HDD/RAID arrays Tried with current bionic and current bionic-proposed installers wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e ---uname output--- uname -a Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:05:20 UTC 2018 ppc64le GNU/Linux Machine Type = 8247-22L (S822L) ---boot type--- Network boot ---bootloader--- petitboot shell ---Kernel cmdline used to launch install--- #cat /proc/cmdline ---Bootloader protocol--- http ---Install repository type--- Internet repository ---Install repository Location--- US ---Point of failure--- Problem during post-install (stage 2) configuration or other problem seen after reboot ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM ? ? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ? ? ? ?? ? ? ??? moves; selects; activates buttons ~ # lsmod | grep -i ipr ipr 148677 0 ~ # modinfo ipr filename: /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko version:2.6.4 license:GPL description:IBM Power RAID SCSI Adapter Driver author: Brian Kingsrcversion: 05BB872A11F65B3A73AB352 alias: pci:v1014d04DAsv1014sd04FBbc*sc*i* alias: pci:v1014d04DAsv1014sd04FCbc*sc*i* alias: pci:v1014d034Asv1014sd04C9bc*sc*i* alias: pci:v1014d034Asv1014sd04C8bc*sc*i* alias: pci:v1014d034Asv1014sd04C7bc*sc*i* alias: pci:v1014d034Asv1014sd049Cbc*sc*i* alias: pci:v1014d034Asv1014sd049Bbc*sc*i* alias: pci:v1014d034Asv1014sd049Abc*sc*i* alias: pci:v1014d034Asv1014sd0499bc*sc*i* alias: pci:v1014d034Asv1014sd0475bc*sc*i* alias: pci:v1014d034Asv1014sd0474bc*sc*i* alias: pci:v1014d034Asv1014sd04CAbc*sc*i* alias:
[Kernel-packages] [Bug 1764794] 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 1764794 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/1764794 Title: signing: only install a signed kernel Status in linux package in Ubuntu: Incomplete Bug description: We should switch the default kernle install to the signed kernel. This makes it much harder to uninstall the signed kernel in environments which enforce the kernel to be signed. Boot loaders which can understand and validate it want the signed image, those which do not should ignore the appended signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764794] [NEW] signing: only install a signed kernel
Public bug reported: We should switch the default kernle install to the signed kernel. This makes it much harder to uninstall the signed kernel in environments which enforce the kernel to be signed. Boot loaders which can understand and validate it want the signed image, those which do not should ignore the appended signature. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1764794 Title: signing: only install a signed kernel Status in linux package in Ubuntu: Incomplete Bug description: We should switch the default kernle install to the signed kernel. This makes it much harder to uninstall the signed kernel in environments which enforce the kernel to be signed. Boot loaders which can understand and validate it want the signed image, those which do not should ignore the appended signature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1568729 Title: divide error: [#1] SMP in task_numa_migrate - handle_mm_fault Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Bug description: While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1 the host system has crashed (load > 200) 3 times in the last 3 days. Always with this stack trace: Apr 9 19:01:09 cnode9.0 kernel: [197071.195577] divide error: [#1] SMP Apr 9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net vhost macvtap macvlan arc4 md4 nls_utf8 ci fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_fil ter ip6_tables iptable_mangle xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables dum my bridge stp llc ipmi_ssif ipmi_devintf intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dcdbas irqbypass crct10dif_p clmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev input_leds nf_nat_ftp sb_edac nf_conntrack_ftp e dac_core cdc_ether nf_nat_pptp usbnet nf_conntrack_pptp mii nf_nat_proto_gre lpc_ich nf_nat_sip ioatdma nf_nat nf_conntrack_sip nfsd ipmi_si 8250_fintek nf_conntrack_proto_gre ipmi_msghandler acpi_pad wmi shpchp nf_conntrack acpi_power_meter mac_hid auth_rpcgss nfs_acl bonding nfs lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs hid_generic usbhid hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_ xor async_tx xor ixgbe raid6_pq libcrc32c igb vxlan raid1 i2c_algo_bit ip6_udp_tunnel dca udp_tunnel ahci raid0 ptp libahci megaraid_sas mult ipath pps_core mdio linear fjes Apr 9 19:01:09 cnode9.0 kernel: [197071.197014] CPU: 13 PID: 3147726 Comm: ceph-osd Not tainted 4.4.0-15-generic #31~14 .04.1-Ubuntu Apr 9 19:01:09 cnode9.0 kernel: [197071.197085] Hardware name: Dell Inc. PowerEdge R720/0XH7F2, BIOS 2.5.2 01/28/2015 Apr 9 19:01:09 cnode9.0 kernel: [197071.197154] task: 88252be1ee00 ti: 8824fc0d4000 task.ti: 8824fc0d4000 Apr 9 19:01:09 cnode9.0 kernel: [197071.197221] RIP: 0010:[] [] task_numa_find_cpu+0x238/0x700 Apr 9 19:01:09 cnode9.0 kernel: [197071.197300] RSP: :8824fc0d7ba8 EFLAGS: 00010257 Apr 9 19:01:09 cnode9.0 kernel: [197071.197340] RAX: RBX: 8824fc0d7c48 RCX: Apr 9 19:01:09 cnode9.0 kernel: [197071.197406] RDX: RSI: 88479f18 RDI: 884782a47600 Apr 9 19:01:09 cnode9.0 kernel: [197071.197473] RBP: 8824fc0d7c10 R08: 000102eea157 R09: 01a8 Apr 9 19:01:09 cnode9.0 kernel: [197071.197540] R10: 0002404b R11: 023f R12: 88238093 Apr 9 19:01:09 cnode9.0 kernel: [197071.197606] R13: 0008 R14: 008c R15: 0124 Apr 9 19:01:09 cnode9.0 kernel: [197071.197673] FS: 7f19aab5b700() GS:88479f18() knlGS: Apr 9 19:01:09 cnode9.0 kernel: [197071.197741] CS: 0010 DS: ES: CR0: 80050033 Apr 9 19:01:09 cnode9.0 kernel: [197071.197782] CR2: 25469600 CR3: 0023846bc000 CR4: 000426e0 Apr 9 19:01:09 cnode9.0 kernel: [197071.197848] Stack: Apr 9 19:01:09 cnode9.0 kernel: [197071.197880] 817425fb 8829af3e9e00 00f6 88252be1ee00 Apr 9 19:01:09 cnode9.0 kernel: [197071.197965] 008d 0225 00016d40 008d Apr 9 19:01:09 cnode9.0 kernel: [197071.198047] 88252be1ee00 01ad 8824fc0d7c48 00e1 Apr 9 19:01:09 cnode9.0 kernel: [197071.198132] Call Trace: Apr 9 19:01:09 cnode9.0 kernel: [197071.198172] [] ? tcp_schedule_loss_probe+0x12b/0x1b0 Apr 9 19:01:09 cnode9.0 kernel: [197071.198219] [] task_numa_migrate+0x4a0/0x930 Apr 9 19:01:09 cnode9.0 kernel: [197071.198264] [] ? release_sock+0x117/0x160 Apr 9 19:01:09 cnode9.0 kernel: [197071.198306] [] numa_migrate_preferred+0x79/0x80 Apr 9 19:01:09 cnode9.0 kernel: [197071.198350] [] task_numa_fault+0x91d/0xcc0 Apr 9 19:01:09 cnode9.0 kernel: [197071.198395] [] ? mpol_misplaced+0x14e/0x190 Apr 9 19:01:09 cnode9.0 kernel: [197071.198439] [] handle_pte_fault+0x5a8/0x14c0 Apr 9 19:01:09 cnode9.0 kernel: [197071.198485] [] ? futex_wake+0x81/0x150 Apr 9 19:01:09 cnode9.0 kernel: [197071.198526] [] ? set_next_entity+0xa4/0x700 Apr 9 19:01:09 cnode9.0 kernel: [197071.198569] [] ? do_futex+0xf4/0x4d0
[Kernel-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Ubuntu 18.04 ppc64el installer does detect IPR (IBM Power RAID) based HDD/RAID arrays Tried with current bionic and current bionic-proposed installers wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux wget http://ports.ubuntu.com/ubuntu-ports/dists/bionic-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz kexec -l vmlinux -i initrd.gz kexec -e ---uname output--- uname -a Linux ltciofvtr-s822l2-lp1 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:05:20 UTC 2018 ppc64le GNU/Linux Machine Type = 8247-22L (S822L) ---boot type--- Network boot ---bootloader--- petitboot shell ---Kernel cmdline used to launch install--- #cat /proc/cmdline ---Bootloader protocol--- http ---Install repository type--- Internet repository ---Install repository Location--- US ---Point of failure--- Problem during post-install (stage 2) configuration or other problem seen after reboot ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? SCSI1 (0,0,0) (sda) - 2.0 GB SMART USB-IBM ? ? SCSI2 (0,0,0) (sdb) - 1.0 TB IBM T RDX-USB3 ? ? ? ?? ? ? ??? moves; selects; activates buttons ~ # lsmod | grep -i ipr ipr 148677 0 ~ # modinfo ipr filename: /lib/modules/4.13.0-32-generic/kernel/drivers/scsi/ipr.ko version:2.6.4 license:GPL description:IBM Power RAID SCSI Adapter Driver author: Brian Kingsrcversion: 05BB872A11F65B3A73AB352 alias: pci:v1014d04DAsv1014sd04FBbc*sc*i* alias: pci:v1014d04DAsv1014sd04FCbc*sc*i* alias: pci:v1014d034Asv1014sd04C9bc*sc*i* alias: pci:v1014d034Asv1014sd04C8bc*sc*i* alias: pci:v1014d034Asv1014sd04C7bc*sc*i* alias: pci:v1014d034Asv1014sd049Cbc*sc*i* alias: pci:v1014d034Asv1014sd049Bbc*sc*i* alias: pci:v1014d034Asv1014sd049Abc*sc*i* alias: pci:v1014d034Asv1014sd0499bc*sc*i* alias: pci:v1014d034Asv1014sd0475bc*sc*i* alias: pci:v1014d034Asv1014sd0474bc*sc*i* alias: pci:v1014d034Asv1014sd04CAbc*sc*i* alias: pci:v1014d034Asv1014sd046Dbc*sc*i* alias: pci:v1014d034Asv1014sd03FEbc*sc*i* alias: pci:v1014d034Asv1014sd03FFbc*sc*i* alias: pci:v1014d034Asv1014sd03FCbc*sc*i* alias: pci:v1014d034Asv1014sd03FBbc*sc*i* alias: pci:v1014d034Asv1014sd035Ebc*sc*i* alias: pci:v1014d034Asv1014sd035Dbc*sc*i* alias: pci:v1014d034Asv1014sd0357bc*sc*i* alias: pci:v1014d034Asv1014sd0355bc*sc*i* alias: pci:v1014d034Asv1014sd033Bbc*sc*i* alias: pci:v1014d033Dsv1014sd0354bc*sc*i* alias:
[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU
I built an Artful test kernel with a back port of commit 947134d9b00. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1747134 Can you test this kernel and see if it resolves this bug? Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages. I'll also work on getting a back port and identify prereq commits for Xenial. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in intel: New 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: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1747134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764498] Re: linux: 4.15.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1764505 (linux-hwe-edge) derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 (linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 (linux-kvm) + kernel-phase:Uploaded + kernel-phase-changed:Tuesday, 17. April 2018 16:00 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 backports: bug 1764505 (linux-hwe-edge) derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 (linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 (linux-kvm) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 17. April 2018 16:00 UTC + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764498 Title: linux: 4.15.0-17.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1764505 (linux-hwe-edge) derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 (linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 (linux-kvm) kernel-phase:Uploaded kernel-phase-changed:Tuesday, 17. April 2018 16:00 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1764498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764504] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-master-bug: 1764498 + kernel-phase:Packaging + kernel-phase-changed:Tuesday, 17. April 2018 16:01 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 -- kernel-master-bug: 1764498 - kernel-phase:Packaging - kernel-phase-changed:Tuesday, 17. April 2018 16:01 UTC + phase: Packaging -- 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/1764504 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1764498 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1764504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764501] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 -- kernel-master-bug: 1764498 + kernel-phase:Packaging + kernel-phase-changed:Tuesday, 17. April 2018 16:01 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 -- kernel-master-bug: 1764498 - kernel-phase:Packaging - kernel-phase-changed:Tuesday, 17. April 2018 16:01 UTC + phase: Packaging -- 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/1764501 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1764498 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1764501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764792] [NEW] Build Nvidia drivers in conjunction with kernel
Public bug reported: We want to deliver a great out of the box experience of Ubuntu users running on Nvidia GPU enabled platforms (including instances in the cloud). Can we explore the possibility of pre-building the nvidia drivers alongside the kernel build, but not pre-link the drivers. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764792 Title: Build Nvidia drivers in conjunction with kernel Status in linux package in Ubuntu: New Bug description: We want to deliver a great out of the box experience of Ubuntu users running on Nvidia GPU enabled platforms (including instances in the cloud). Can we explore the possibility of pre-building the nvidia drivers alongside the kernel build, but not pre-link the drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729085] Comment bridged from LTC Bugzilla
--- Comment From tlfal...@us.ibm.com 2018-04-17 11:47 EDT--- Thanks, closing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729085 Title: [18.04] Missing vNIC module in the installer Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Mirroring over for 18.04 installer. Canonical: Please add the ibmvnic module to the installer for 18.04. Thank you. == Comment: #0 - YUECHANG E. MEI - 2017-02-27 11:33:10 == ---Problem Description--- We tried to install ubuntu 16.04.2 by using vNIC. When we tried to load the installer, we saw an issue. Comment from bug 144675, it looks like the ibmvnic module is not included in 16.04.2 or 17.04 installer. GNU GRUB version 2.02~beta2-vlan1 ++ | Install Ubuntu 17.04 GA w/ multipath and preseed | | Install Ubuntu 17.04 GA w/ multipath | | Install Ubuntu 17.04 GA w/ preseed | |*Install Ubuntu Yakkety (16.10 development) | | Install Ubuntu Yakkety (16.10 w/ multipath) | | Install Ubuntu 16.04 GA | | Install Ubuntu 16.04 GA w/ multipath | | Install Ubuntu 16.04 GA w/ preseed | | Install Ubuntu 16.04 GA w/ multipath and preseed | | Install Ubuntu 14.04.4 LTS | | Install Ubuntu 14.04.5 LTS | | Rescue mode | ++ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. ?? [!!] Download debconf preconfiguration file ?? ? ? ? Failed to retrieve the preconfiguration file ? ? The file needed for preconfiguration could not be retrieved from ? ? http://10.33.11.31/distros/ubuntu/preseed.cfg. The installation will ? ? proceed in non-automated mode.? ? ? ? ? ? ? ? but then we cannot go any further...drop to the shell and we do not see any ibmvnic loaded, try to load it is not found. ~ # lsmod|grep ibm ibmveth31190 0 ~ # modprobe ibmvnic modprobe: FATAL: Module ibmvnic not found in directory /lib/modules/4.4.0-21-generic ~ # ---boot type--- Network boot ---bootloader--- grub ---Point of failure--- Failed during boot of installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1729085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747273] Re: Can not control brightness on Thinkpad P51
ping Michael and Urschl ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1747273 Title: Can not control brightness on Thinkpad P51 Status in linux package in Ubuntu: Incomplete Bug description: I can not modify the screen brightness in Ubuntu 17.10. Controls aside, the classes in `proc` are either not available or non- functional depending on what arguments I provide in GRUB_CMDLINE_LINUX_DEFAULT. On a parallel installation (Ubuntu 16.04.3), brightness control works flawlessly. System Information -- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Device a171 (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux thinkpad-acpi.brightness_enable=1": $ grep . -R /sys/class/backlight/thinkpad_screen/* /sys/class/backlight/thinkpad_screen/actual_brightness:0 /sys/class/backlight/thinkpad_screen/bl_power:0 /sys/class/backlight/thinkpad_screen/brightness:11 /sys/class/backlight/thinkpad_screen/max_brightness:15 /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0 /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0 grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: Input/output error /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0 /sys/class/backlight/thinkpad_screen/power/control:auto /sys/class/backlight/thinkpad_screen/power/async:disabled /sys/class/backlight/thinkpad_screen/power/runtime_usage:0 /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported grep: warning: /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: recursive directory loop /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0 grep: /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms: Input/output error /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/max_brightness:15
[Kernel-packages] [Bug 1764515] Re: wifi crashes in ubuntu 16.04 lts xenial
** Description changed: + I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. + When I installed ubuntustudio afresh, wifi was alright until recently, everyone time I connect to my blackberry mobile hotspot, it pops the dialog that "the wifi key is needed for authentication" repeatedly, so it never gets connected to the internet through my phone. + I have tried reinstalling network manager, restart service through the command line , boot and reboot, added [device] wifi.scan.rand line to network*.conf. + All I mentioned above didnt work - I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When I installed afresh, wifi was alright until recently, everyone time I connect, it pops the dialog that the wifi key is needed for authentication over and again, so it never gets connected to the internet.i have tried reinstalling network manager, service restart, boot and reboot, adding [device] wifi.scan nothing worked - What do I need? I barely use windows now 'Cause linux is just dope... + What do I need do? I barely use windows now 'Cause linux is just + dope...' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764515 Title: wifi crashes in ubuntu 16.04 lts xenial Status in linux package in Ubuntu: Opinion Status in network-manager package in Ubuntu: New Bug description: I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When I installed ubuntustudio afresh, wifi was alright until recently, everyone time I connect to my blackberry mobile hotspot, it pops the dialog that "the wifi key is needed for authentication" repeatedly, so it never gets connected to the internet through my phone. I have tried reinstalling network manager, restart service through the command line , boot and reboot, added [device] wifi.scan.rand line to network*.conf. All I mentioned above didnt work What do I need do? I barely use windows now 'Cause linux is just dope...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
(I used my team account cloudstackers-7 before, now with my own one) The bounds check may not be necessary, because replace_map_fd_with_map_ptr is called before do_check and the relevant check is already in replace_map_fd_with_map_ptr. But it's not obvious, so at least a comment in do_check may be a good idea. -- You 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: Triaged Status in linux source package in Xenial: Triaged 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] [] ? __schedule+0x30d/0x7f0 [ 62.410491] [] ? __schedule+0x301/0x7f0 [ 62.431220] [] ? __schedule+0x30d/0x7f0 [ 62.497078] [] ? __schedule+0x30d/0x7f0 [ 62.559245] [] ? __schedule+0x301/0x7f0 [ 62.661493] [] ? __schedule+0x30d/0x7f0 [ 62.712927] [] ? __schedule+0x301/0x7f0 [ 62.799216] [] trace_call_bpf+0x37/0x50 [
[Kernel-packages] [Bug 1763454] Re: bpf_map_lookup_elem: BUG: unable to handle kernel paging request
I've duped the other bug to this one. I do agree that the "seen = true" you identified looks like a mistake, I will fix up the patch to remove that. You also added some bounds checking. I see your point in adding that, I can't find anything which would guarantee that there is an additional instruction there. However the check_ld_imm() call before that can also assume that there's something after the current instruction, so either there is some guarantee that there's something after the current instruction or else that bounds check needs to be moved. As the upstream source still lacks a bounds check there too, it might be best to pursue this question upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763454 Title: bpf_map_lookup_elem: BUG: unable to handle kernel paging request Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged 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 1764515] Re: wifi crashes in ubuntu 16.04 lts xenial
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764515 Title: wifi crashes in ubuntu 16.04 lts xenial Status in linux package in Ubuntu: Opinion Status in network-manager package in Ubuntu: New Bug description: I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When I installed afresh, wifi was alright until recently, everyone time I connect, it pops the dialog that the wifi key is needed for authentication over and again, so it never gets connected to the internet.i have tried reinstalling network manager, service restart, boot and reboot, adding [device] wifi.scan nothing worked What do I need? I barely use windows now 'Cause linux is just dope... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722261] Re: deadlock in mount umount and sync
Couple of things: 1. Next time this occurs, can you run the following command and paste the output into the bug report: sudo zpool events -v That may provide some additional information on what state the IOs are in. 2. If you are using ZFS intent log, it may be worth trying to set it to a fairly large size, such as 128 or 256MB using the zil_slog_limit setting -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1722261 Title: deadlock in mount umount and sync Status in zfs-linux package in Ubuntu: Incomplete Bug description: I use zfs vesion 0.6.5.6 on Ubuntu 16.04.2 LTS . I have many zombie process on auto-mount of snapshot and on sync ! 903 process are in deadlock. i can't mount a new file system or snapshot . Partial output of ps alx |grep 'call_r D' below . what is the cause? what can I do ? 0 0 2371 1 20 0 6016 752 call_r D? 0:00 /bin/sync 0 0 15290 1 20 0 6016 676 call_r D? 0:00 /bin/sync 0 0 18919 1 20 0 6016 708 call_r D? 0:00 /bin/sync 0 0 27076 1 20 0 6016 808 call_r D? 0:00 /bin/sync 4 0 31976 1 20 0 22084 1344 call_r D? 0:00 umount -t zfs -n /samba/shares/Aat/.zfs/snapshot/2017-10-04_09.00.05--5d error in kern.log: 9 13:20:28 zfs-cis kernel: [5368563.592834] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:20:28 zfs-cis kernel: [5368563.597868] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:20:28 zfs-cis kernel: [5368563.601730] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_08.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_08.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.187001] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.13] WARNING: Unable to automount /samba/shares/Cardiologia2/.zfs/snapshot/2017-10-03_12.00.03--5d/pool_z2_samba/shares/Cardiologia2@2017-10-03_12.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.15] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.189005] WARNING: Unable to automount /samba/shares/Aat/.zfs/snapshot/2017-10-03_20.00.04--5d/pool_z2_samba/shares/Aat@2017-10-03_20.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.190105] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.192847] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_10.00.03--5d/pool_z2_samba/shares/Trapianti@2017-10-03_10.00.03--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.193617] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 Oct 9 13:22:57 zfs-cis kernel: [5368713.198096] WARNING: Unable to automount /samba/shares/Trapianti/.zfs/snapshot/2017-10-03_14.00.04--5d/pool_z2_samba/shares/Trapianti@2017-10-03_14.00.04--5d: 256 in syslog : Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dChtrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=155 reply_cookie=0 error=n/a Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dLaboratorio_5fTrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=202 reply_cookie=0 error=n/a Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dProgettoTrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=260 reply_cookie=0 error=n/a Oct 9 12:22:12 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1/unit/samba_2dshares_2dTrapianti_2emount interface=org.freedesktop.DBus.Properties member=GetAll cookie=291 reply_cookie=0 error=n/a Oct 9 12:22:13 zfs-cis systemd[1]: Got message type=method_call sender=n/a destination=org.freedesktop.systemd1
[Kernel-packages] [Bug 1763352] Re: kernel panic in bpf_map_update_elem (with bcc tool ext4slower)
*** This bug is a duplicate of bug 1763454 *** https://bugs.launchpad.net/bugs/1763454 ** This bug has been marked a duplicate of bug 1763454 bpf_map_lookup_elem: BUG: unable to handle kernel paging request -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763352 Title: kernel panic in bpf_map_update_elem (with bcc tool ext4slower) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Using Ubuntu 16.04 LTS with 4.4.0 kernel on x86_64 After kernel update from 4.4.0-116 to 4.4.0-119 running an eBPF tool to log slow ext4 I/O (bcc-tool ext4slower) causes a kernel panic in bpf_map_update_elem. Steps to reproduce: * install bcc-tools 0.5.0-1 (https://github.com/iovisor/bcc), packages: bcc-tools, libbcc, python-bcc, libbcc-examples; from repo.iovisor.org * install kernel 4.4.0-119 (linux-image-4.4.0-119-generic linux-image-extra-4.4.0-119 linux-headers-4.4.0-119 linux-headers-4.4.0-119-generic) * reboot * run ext4slower (sudo /usr/share/bcc/tools/ext4slower) * system crashes With kernel 4.4.0-116 ext4slower runs fine. uname -a: Linux 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux BCC tools version: 0.5.0-1 Log of the kernel panic including backtrace: [ 59.635900] BUG: unable to handle kernel paging request at b98aa6a8 [ 59.642345] IP: [] bpf_map_update_elem+0x6/0x20 [ 59.645782] PGD 0 [ 59.647150] Oops: [#1] SMP [ 59.649808] Modules linked in: crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 8250_fintek parport_pc parport mac_hid autofs4 hid_generic usbhid hid ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm pata_acpi floppy [ 59.672373] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-119-generic #143-Ubuntu [ 59.676407] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-2 04/01/2014 [ 59.680079] task: 88013a49 ti: 88013a48c000 task.ti: 88013a48c000 [ 59.684124] RIP: 0010:[] [] bpf_map_update_elem+0x6/0x20 [ 59.689097] RSP: 0018:88013a48f980 EFLAGS: 00010086 [ 59.691618] RAX: 8117cd90 RBX: c9818170 RCX: [ 59.695739] RDX: 88013a48fbd0 RSI: 88013a48fbe8 RDI: b98aa680 [ 59.699444] RBP: 88013a48fc08 R08: 880138d6b180 R09: 0800 [ 59.703264] R10: 88013a49 R11: 0246 R12: [ 59.707164] R13: 8800ba0f4400 R14: 88013fc10020 R15: 88013a48fd58 [ 59.72] FS: 7f4039da58c0() GS:88013fc0() knlGS: [ 59.715861] CS: 0010 DS: ES: CR0: 80050033 [ 59.719025] CR2: b98aa6a8 CR3: bb65e000 CR4: 00160670 [ 59.722937] DR0: DR1: DR2: [ 59.727210] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.731074] Stack: [ 59.732149] 88013a48fc08 81177411 88013fc20500 [ 59.735760] b98aa680 88013a48fbe8 88013a48fbd0 [ 59.740058] 880138d6b180 88013a48fe58 8800bb5ab000 [ 59.744100] Call Trace: [ 59.745434] [] ? __bpf_prog_run+0x7a1/0x1360 [ 59.748289] [] ? update_curr+0x79/0x170 [ 59.751044] [] ? vp_notify+0x16/0x20 [ 59.753601] [] ? dequeue_entity+0x41b/0xa80 [ 59.756354] [] ? update_load_avg+0x219/0x7d0 [ 59.759171] [] ? set_next_entity+0x9c/0xb0 [ 59.761890] [] ? __switch_to+0x1dc/0x5c0 [ 59.764667] [] ? __schedule+0x341/0x7f0 [ 59.767155] [] ? blk_mq_flush_plug_list+0x128/0x150 [ 59.770253] [] ? bit_wait+0x60/0x60 [ 59.772782] [] trace_call_bpf+0x37/0x50 [ 59.775336] [] kprobe_perf_func+0x37/0x250 [ 59.778264] [] ? ktime_get+0x3e/0xb0 [ 59.780724] [] ? delayacct_end+0x56/0x60 [ 59.783589] [] kprobe_dispatcher+0x31/0x50 [ 59.786490] [] aggr_pre_handler+0x45/0x80 [ 59.789534] [] ? generic_file_read_iter+0x1/0x690 [ 59.792407] [] kprobe_ftrace_handler+0xb6/0x120 [ 59.795329] [] ? generic_file_read_iter+0x5/0x690 [ 59.798453] [] ftrace_ops_recurs_func+0x58/0xb0 [ 59.801948] [] 0xc00180d5 [ 59.804357] [] ? filemap_write_and_wait_range+0x70/0x70 [ 59.808022] [] ? generic_file_read_iter+0x1/0x690 [ 59.811225] [] generic_file_read_iter+0x5/0x690 [ 59.814332] [] new_sync_read+0x9e/0xe0 [ 59.817079] [] ? generic_file_read_iter+0x5/0x690 [ 59.820120] [] ? kretprobe_trampoline_holder+0x9/0x9 [ 59.825007] [] __vfs_read+0x29/0x40 [ 59.827528] [] vfs_read+0x86/0x130 [ 59.829931] []
[Kernel-packages] [Bug 1752536] Re: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic
Changing to affect linux package. The firmware is present but the driver lacks the MODULE_FIRMWARE statement to get the firmware placed into the initrd. ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752536 Title: i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel 4.4.0-116-generic Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Bug description: :~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial :~$ uname -r 4.4.0-116-generic The problem :~$ dmesg | grep i915 [0.991220] [drm:i915_dump_device_info] i915 device info: gen=9, pciid=0x5902 rev=0x04 flags=need_gfx_hws,is_kabylake,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg, [0.991711] [drm:i915_gem_init_stolen] Memory reserved for graphics device: 65536K, usable: 64512K [0.992136] [drm:i915_ggtt_init_hw] GMADR size = 256M [0.992137] [drm:i915_ggtt_init_hw] GTT stolen size = 64M [0.992138] [drm:i915_ggtt_init_hw] ppgtt mode: 3 [1.001094] [drm:intel_csr_ucode_init] Loading i915/kbl_dmc_ver1.bin [1.001114] i915_bpo :00:02.0: Direct firmware load for i915/kbl_dmc_ver1.bin failed with error -2 [1.001119] i915_bpo :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling runtime power management. [1.005895] [drm:i915_gem_object_create_stolen_for_preallocated] creating preallocated stolen object: stolen_offset=0, gtt_offset=0, size=408000 [1.005897] [drm:i915_pages_create_for_stolen] offset=0x0, size=4227072 [1.006228] [drm:i915_gem_setup_global_gtt] reserving preallocated space: 0 + 408000 [1.006230] [drm:i915_gem_setup_global_gtt] clearing unused GTT space: [408000, f000] [1.007450] [drm:i915_gem_context_init] LR context support initialized [1.010861] [drm] Initialized i915_bpo 1.6.0 20160425 for :00:02.0 on minor 0 [1.857985] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device [ 11.248704] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915_bpo]) [ 18.739304] [drm:i915_gem_open] [ 18.739408] [drm:i915_gem_open] [ 18.739484] [drm:i915_gem_open] [ 18.739524] [drm:i915_gem_open] [ 33.631792] [drm:i915_gem_open] [ 35.515257] [drm:i915_gem_open] [ 35.582793] [drm:i915_gem_open] [ 42.823681] [drm:i915_gem_open] [ 47.557725] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.565183] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.566992] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.573099] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.574721] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 47.581074] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.035670] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.044499] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.046373] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.052451] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.054246] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 960.060454] [drm:i915_audio_component_sync_audio_rate] Not valid for port C [ 969.549771] [drm:i915_gem_open] [ 969.704665] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 969.794654] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1125.305318] [drm:i915_gem_open] [ 1125.328165] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1125.333583] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1227.799188] [drm:i915_gem_open] [ 1227.806911] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1227.807865] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1436.623061] [drm:i915_gem_open] [ 1436.629327] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1436.630138] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed [ 1459.597494] [drm:i915_gem_open] [ 1459.603754] [drm:i915_gem_context_create_ioctl] HW context 1 created [ 1459.604550]
[Kernel-packages] [Bug 1744173] Re: artful: rfi-flush: Switch to new linear fallback flush
** Changed in: ubuntu-power-systems Status: Triaged => 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/1744173 Title: artful: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress 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 Bug description: Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764762] [NEW] Xenial update to 4.4.124 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.124 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.124 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) 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/1764762 Title: Xenial update to 4.4.124 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.124 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.124 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Seth, I reported the same issue in LP#1763352 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763352). My patch there does essentially the same as yours, so I will mention in that ticket that it's a duplicate. But your patch does not remove the wrong "env->insn_aux_data[insn_idx].seen = true" from kernel/bpf/verifier.c line 1844. I think that "seen" shouldn't be set there. The line was probably added there by mistake. It should have been added for the LD IMM64 case in the first place. -- You 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: Triaged Status in linux source package in Xenial: Triaged 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] [] ? __schedule+0x30d/0x7f0 [ 62.410491] [] ? __schedule+0x301/0x7f0 [ 62.431220] [] ? __schedule+0x30d/0x7f0 [ 62.497078] [] ? __schedule+0x30d/0x7f0 [
[Kernel-packages] [Bug 1763352] Re: kernel panic in bpf_map_update_elem (with bcc tool ext4slower)
The same issue was reported in LP#1763454 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763454 Seth Forshee provided a patch there that solves the issue here as well. His patch has been sent to the mailing list already. >From my point of view we could treat this ticket here as a duplicate of LP#1763454 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763352 Title: kernel panic in bpf_map_update_elem (with bcc tool ext4slower) Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Using Ubuntu 16.04 LTS with 4.4.0 kernel on x86_64 After kernel update from 4.4.0-116 to 4.4.0-119 running an eBPF tool to log slow ext4 I/O (bcc-tool ext4slower) causes a kernel panic in bpf_map_update_elem. Steps to reproduce: * install bcc-tools 0.5.0-1 (https://github.com/iovisor/bcc), packages: bcc-tools, libbcc, python-bcc, libbcc-examples; from repo.iovisor.org * install kernel 4.4.0-119 (linux-image-4.4.0-119-generic linux-image-extra-4.4.0-119 linux-headers-4.4.0-119 linux-headers-4.4.0-119-generic) * reboot * run ext4slower (sudo /usr/share/bcc/tools/ext4slower) * system crashes With kernel 4.4.0-116 ext4slower runs fine. uname -a: Linux 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux BCC tools version: 0.5.0-1 Log of the kernel panic including backtrace: [ 59.635900] BUG: unable to handle kernel paging request at b98aa6a8 [ 59.642345] IP: [] bpf_map_update_elem+0x6/0x20 [ 59.645782] PGD 0 [ 59.647150] Oops: [#1] SMP [ 59.649808] Modules linked in: crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 8250_fintek parport_pc parport mac_hid autofs4 hid_generic usbhid hid ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm pata_acpi floppy [ 59.672373] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-119-generic #143-Ubuntu [ 59.676407] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.2-2 04/01/2014 [ 59.680079] task: 88013a49 ti: 88013a48c000 task.ti: 88013a48c000 [ 59.684124] RIP: 0010:[] [] bpf_map_update_elem+0x6/0x20 [ 59.689097] RSP: 0018:88013a48f980 EFLAGS: 00010086 [ 59.691618] RAX: 8117cd90 RBX: c9818170 RCX: [ 59.695739] RDX: 88013a48fbd0 RSI: 88013a48fbe8 RDI: b98aa680 [ 59.699444] RBP: 88013a48fc08 R08: 880138d6b180 R09: 0800 [ 59.703264] R10: 88013a49 R11: 0246 R12: [ 59.707164] R13: 8800ba0f4400 R14: 88013fc10020 R15: 88013a48fd58 [ 59.72] FS: 7f4039da58c0() GS:88013fc0() knlGS: [ 59.715861] CS: 0010 DS: ES: CR0: 80050033 [ 59.719025] CR2: b98aa6a8 CR3: bb65e000 CR4: 00160670 [ 59.722937] DR0: DR1: DR2: [ 59.727210] DR3: DR6: fffe0ff0 DR7: 0400 [ 59.731074] Stack: [ 59.732149] 88013a48fc08 81177411 88013fc20500 [ 59.735760] b98aa680 88013a48fbe8 88013a48fbd0 [ 59.740058] 880138d6b180 88013a48fe58 8800bb5ab000 [ 59.744100] Call Trace: [ 59.745434] [] ? __bpf_prog_run+0x7a1/0x1360 [ 59.748289] [] ? update_curr+0x79/0x170 [ 59.751044] [] ? vp_notify+0x16/0x20 [ 59.753601] [] ? dequeue_entity+0x41b/0xa80 [ 59.756354] [] ? update_load_avg+0x219/0x7d0 [ 59.759171] [] ? set_next_entity+0x9c/0xb0 [ 59.761890] [] ? __switch_to+0x1dc/0x5c0 [ 59.764667] [] ? __schedule+0x341/0x7f0 [ 59.767155] [] ? blk_mq_flush_plug_list+0x128/0x150 [ 59.770253] [] ? bit_wait+0x60/0x60 [ 59.772782] [] trace_call_bpf+0x37/0x50 [ 59.775336] [] kprobe_perf_func+0x37/0x250 [ 59.778264] [] ? ktime_get+0x3e/0xb0 [ 59.780724] [] ? delayacct_end+0x56/0x60 [ 59.783589] [] kprobe_dispatcher+0x31/0x50 [ 59.786490] [] aggr_pre_handler+0x45/0x80 [ 59.789534] [] ? generic_file_read_iter+0x1/0x690 [ 59.792407] [] kprobe_ftrace_handler+0xb6/0x120 [ 59.795329] [] ? generic_file_read_iter+0x5/0x690 [ 59.798453] [] ftrace_ops_recurs_func+0x58/0xb0 [ 59.801948] [] 0xc00180d5 [ 59.804357] [] ? filemap_write_and_wait_range+0x70/0x70 [ 59.808022] [] ? generic_file_read_iter+0x1/0x690 [ 59.811225] [] generic_file_read_iter+0x5/0x690 [ 59.814332] [] new_sync_read+0x9e/0xe0 [ 59.817079] [] ? generic_file_read_iter+0x5/0x690 [ 59.820120] [] ? kretprobe_trampoline_holder+0x9/0x9 [
[Kernel-packages] [Bug 1764744] Re: Support of freeipa-server for s390x
** Package changed: linux (Ubuntu) => freeipa (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/1764744 Title: Support of freeipa-server for s390x Status in Ubuntu on IBM z Systems: Triaged Status in freeipa package in Ubuntu: New Bug description: freeipa fails to configure on s390x. (Configuration being handled by the freeipa-server-install script)This script has two failure points. The first is below: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1600634 describes a known bug but it was only resolved for x86_64. In the falling scenario the install log will have entries like the following: 2018-04-10T18:53:01Z DEBUG nsslapd-pluginenabled: 2018-04-10T18:53:01Z DEBUG on 2018-04-10T18:53:01Z DEBUG nsslapd-pluginpath: 2018-04-10T18:53:01Z DEBUG /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so 2018-04-10T18:53:01Z DEBUG nsslapd-pluginversion: 2018-04-10T18:53:01Z DEBUG 0.8 Obviously on s390x /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so will never be found. Now if I create a symbolic link with the above name that is linked to the same location but with s390x where x86_64 is located, the install will proceed past this failing location. The second failure point in the freeipa-server-install script is near the end, after the script has completed the freeipa-server-install and where it attempts to install the freeipa-client. The client install appears to fail because of a problem with certificates related to the server install. 2018-04-17T12:14:59Z ERROR Cannot connect to the server due to generic error: Insufficient access: SASL(-4): no mechanism available: No worthy mechs found (Unknown authentication method) The above appears to be related to an issue with the key database # certutil -L certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format. # ipa cert-show 1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. # ipa user-add First name: Richard >>> First name: Leading and trailing spaces are not allowed First name: Richard Last name: Young User login [ryoung]: ryoung1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1764744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763644] Re: Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware
* linux-snapdragon kernel 4.4.0-1090.95 successfully booted and passed all ADT tests [1] and also snap-certification tests. * linux kernel 4.4.0-121.145 for arm64 successfully booted and passed all ADT tests [2] and successfully booted in our internal arm64 test systems. [1] http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta-snapdragon.html [2] http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta.html ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763644 Title: Ubuntu-4.4.0-120.144 fails to boot on arm64* hardware Status in linux package in Ubuntu: Incomplete Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Fix Committed Bug description: [Impact] The Ubuntu-4.4.0-120.144 kernel (now in -proposed) fails to boot on all arm64 hardware: no console output or any other sign of activity, the system freeze just after the bootloader loads vmlinuz, and jumps to it. We first experienced it on the snapdragon kernel snap in -beta (dragonboard 410c) but the bug is arm64 generic, and it affects all the arm64 hardware: a thunderx board shows the same exact symptoms. The regression came down as part of the 4.4.115 stable update ("79e83d1 bpf: introduce BPF_JIT_ALWAYS_ON config") and enabled this option that crashes the arm64 kernel on boot. [How to test] Apply the attached patch, recompile, install and boot. [Regression potential] None, since the kernel already fails to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763687 Title: linux: 4.4.0-121.145 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa 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 1763688 (linux-lts-xenial) derivatives: bug 1763689 (linux-snapdragon) -- 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/1763687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764666] Re: Xenial update to 4.4.123 stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764666 Title: Xenial update to 4.4.123 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.123 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.123 stable release shall be applied: * Linux 4.4.123 * bpf: fix incorrect sign extension in check_alu_op() * usb: gadget: bdc: 64-bit pointer capability check * USB: gadget: udc: Add missing platform_device_put() on error in bdc_pci_probe() * btrfs: Fix use-after-free when cleaning up fs_devs with a single stale device * btrfs: alloc_chunk: fix DUP stripe size handling * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux * scsi: sg: only check for dxfer_len greater than 256M * scsi: sg: fix static checker warning in sg_is_valid_dxfer * scsi: sg: fix SG_DXFER_FROM_DEV transfers * irqchip/gic-v3-its: Ensure nr_ites >= nr_lpis * fs/aio: Use RCU accessors for kioctx_table->table[] * fs/aio: Add explicit RCU grace period when freeing kioctx * lock_parent() needs to recheck if dentry got __dentry_kill'ed under it * fs: Teach path_connected to handle nfs filesystems with multiple roots. * drm/amdgpu/dce: Don't turn off DP sink when disconnected * ALSA: seq: Clear client entry before deleting else at closing * ALSA: seq: Fix possible UAF in snd_seq_check_queue() * ALSA: hda - Revert power_save option default value * ALSA: pcm: Fix UAF in snd_pcm_oss_get_formats() * x86/mm: Fix vmalloc_fault to use pXd_large * x86/vm86/32: Fix POPF emulation * selftests/x86/entry_from_vm86: Add test cases for POPF * selftests/x86: Add tests for the STR and SLDT instructions * selftests/x86: Add tests for User-Mode Instruction Prevention * selftests/x86/entry_from_vm86: Exit with 1 if we fail * ima: relax requiring a file signature for new files with zero length * rcutorture/configinit: Fix build directory error message * ipvlan: add L2 check for packets arriving via virtual devices * ASoC: nuc900: Fix a loop timeout test * mac80211: remove BUG() when interface type is invalid * mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED * agp/intel: Flush all chipset writes after updating the GGTT * drm/amdkfd: Fix memory leaks in kfd topology * veth: set peer GSO values * media: cpia2: Fix a couple off by one bugs * scsi: dh: add new rdac devices * scsi: devinfo: apply to HP XP the same flags as Hitachi VSP * scsi: core: scsi_get_device_flags_keyed(): Always return device flags * spi: sun6i: disable/unprepare clocks on remove * tools/usbip: fixes build with musl libc toolchain * ath10k: fix invalid STS_CAP_OFFSET_MASK * clk: qcom: msm8916: fix mnd_width for codec_digcodec * cpufreq: Fix governor module removal race * ath10k: update tdls teardown state to target * ARM: dts: omap3-n900: Fix the audio CODEC's reset pin * ARM: dts: am335x-pepper: Fix the audio CODEC's reset pin * mtd: nand: fix interpretation of NAND_CMD_NONE in nand_command[_lp]() * net: xfrm: allow clearing socket xfrm policies. * test_firmware: fix setting old custom fw path back on exit * sched: Stop resched_cpu() from sending IPIs to offline CPUs * sched: Stop switched_to_rt() from sending IPIs to offline CPUs * ARM: dts: exynos: Correct Trats2 panel reset line * HID: elo: clear BTN_LEFT mapping * video/hdmi: Allow "empty" HDMI infoframes * drm/edid: set ELD connector type in drm_edid_to_eld() * wil6210: fix memory access violation in wil_memcpy_from/toio_32 * pwm: tegra: Increase precision in PWM rate calculation * kprobes/x86: Set kprobes pages read-only * kprobes/x86: Fix kprobe-booster not to boost far call instructions * scsi: sg: close race condition in sg_remove_sfp_usercontext() * scsi: sg: check for valid direction before starting the request * perf session: Don't rely on evlist in pipe mode * perf inject: Copy events when reordering events in pipe mode * drivers/perf: arm_pmu: handle no platform_device * usb: gadget: dummy_hcd: Fix wrong power status bit
[Kernel-packages] [Bug 1764755] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764755 Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] Status in linux package in Ubuntu: Confirmed Bug description: my system often hangs, and can not be done anything ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zellkristian 1649 F pulseaudio /dev/snd/controlC0: zellkristian 1649 F pulseaudio Date: Tue Apr 17 00:33:27 2018 Failure: oops InstallationDate: Installed on 2018-04-11 (5 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) MachineType: Quanta TW9/SW9 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2009 dmi.bios.vendor: INSYDE dmi.bios.version: Q3C24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: TW9/SW9 dmi.product.version: 05 dmi.sys.vendor: Quanta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764752] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764752 Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] Status in linux package in Ubuntu: Confirmed Bug description: my system often hangs, and can not be done anything ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zellkristian 1649 F pulseaudio /dev/snd/controlC0: zellkristian 1649 F pulseaudio Date: Tue Apr 17 00:51:45 2018 Failure: oops InstallationDate: Installed on 2018-04-11 (5 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) MachineType: Quanta TW9/SW9 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2009 dmi.bios.vendor: INSYDE dmi.bios.version: Q3C24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: TW9/SW9 dmi.product.version: 05 dmi.sys.vendor: Quanta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764755] [NEW] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0]
Public bug reported: my system often hangs, and can not be done anything ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zellkristian 1649 F pulseaudio /dev/snd/controlC0: zellkristian 1649 F pulseaudio Date: Tue Apr 17 00:33:27 2018 Failure: oops InstallationDate: Installed on 2018-04-11 (5 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) MachineType: Quanta TW9/SW9 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2009 dmi.bios.vendor: INSYDE dmi.bios.version: Q3C24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: TW9/SW9 dmi.product.version: 05 dmi.sys.vendor: Quanta ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-driver-nvidia kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764755 Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] Status in linux package in Ubuntu: Confirmed Bug description: my system often hangs, and can not be done anything ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zellkristian 1649 F pulseaudio /dev/snd/controlC0: zellkristian 1649 F pulseaudio Date: Tue Apr 17 00:33:27 2018 Failure: oops InstallationDate: Installed on 2018-04-11 (5 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) MachineType: Quanta TW9/SW9 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2009 dmi.bios.vendor: INSYDE dmi.bios.version: Q3C24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: TW9/SW9 dmi.product.version: 05 dmi.sys.vendor: Quanta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757193] Re: Boot crash with Trusty 3.13
Confirmed to be fixed with Trusty kernel linux 3.13.0-145.194. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757193 Title: Boot crash with Trusty 3.13 Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: == SRU Justification == Custom compilation of the Trusty 3.13 kernel codebase results in a (reproducible) QEMU boot crash (see below). == Fix == Replace UBUNTU SAUCE patch with proper upstream commit: 548acf19234d ("x86/mm: Expand the exception table logic to allow new handling options") == Regression Potential == Medium. The patch is quite large but the backport was a simple context adjustment. Ran the x86 selftests and perf NMI tests for several hours to verify stability. == Test Case == Compile the Trusty 3.13 kernel code using the default config (make defconfig) and run the resulting kernel in QMEU. Crashes every time. Original bug description: While doing kernel testing using the Trusty 3.13 code base, I get the following boot crash with QEMU: [0.338393] BUG: unable to handle kernel paging request at 014142f0 [0.338987] IP: [] 0x014142f0 [0.339388] PGD 180f067 PUD 0 [0.339388] Oops: 0010 [#1] SMP [0.339388] Modules linked in: [0.339388] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.11-ckt39-trusty #6 [0.339388] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [0.339388] task: 88003f708000 ti: 88003f6fa000 task.ti: 88003f6fa000 [0.339388] RIP: 0010:[] [] 0x014142f0 [0.339388] RSP: :88003f6fbe98 EFLAGS: 00050246 [0.339388] RAX: RBX: RCX: [0.339388] RDX: RSI: 88003deb9eb4 RDI: 818b8590 [0.339388] RBP: 88003f6fbe98 R08: R09: 88003fa14ae0 [0.339388] R10: 81264c68 R11: eafdd000 R12: 818b8590 [0.339388] R13: 00ad R14: R15: [0.339388] FS: () GS:88003fa0() knlGS: [0.339388] CS: 0010 DS: ES: CR0: 80050033 [0.339388] CR2: 014142f0 CR3: 0180c000 CR4: 00360770 [0.339388] DR0: DR1: DR2: [0.339388] DR3: DR6: fffe0ff0 DR7: 0400 [0.339388] Stack: [0.339388] 88003f6fbf08 81000402 88003f6fbf00 81065f88 [0.339388] 88003f6fbef0 88003ffd96a1 817e9d28 00ad00060006 [0.339388] 817b013d 8196cef0 8196d018 0006 [0.339388] Call Trace: [0.339388] [] do_one_initcall+0xf2/0x140 [0.339388] [] ? parse_args+0x1e8/0x320 [0.339388] [] kernel_init_freeable+0x14c/0x1d1 [0.339388] [] ? do_early_param+0x88/0x88 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] [] kernel_init+0x9/0x120 [0.339388] [] ret_from_fork+0x6e/0xa0 [0.339388] [] ? rest_init+0x80/0x80 [0.339388] Code: Bad RIP value. [0.339388] RIP [] 0x014142f0 [0.339388] RSP [0.339388] CR2: 014142f0 [0.339388] ---[ end trace a71242bdac7e8632 ]--- [0.339388] note: swapper/0[1] exited with preempt_count 1 [0.357079] swapper/0 (1) used greatest stack depth: 5424 bytes left [0.357539] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [0.357539] [0.358073] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) Git bisect identified the following commit as the culprit: commit 56764fdc3a847371531b8044155c70412fc5be76 Author: Andy WhitcroftDate: Thu Feb 22 11:24:00 2018 +0100 UBUNTU: SAUCE: x86, extable: fix uaccess fixup detection BugLink: http://bugs.launchpad.net/bugs/1750786 The existing code intends to identify a subset of fixups which need special handling, uaccess related faults need to record the failure. This is done by adjusting the fixup code pointer by a (random) constant 0x7ff0. This is detected in fixup_exception by comparing the two pointers. The intent of this code is to detect the the delta between the original code and its fixup code being greater than the constant. However, the code as written triggers undefined comparison behaviour. In this kernel this prevents the condition triggering, leading to panics when jumping to the corrupted fixup address. Convert the code to better implement
[Kernel-packages] [Bug 1761104] Re: fix regression in mm/hotplug, allows NVIDIA driver to work
** Description changed: == 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))) + 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." -- You 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: In Progress Status in linux source package in Artful: In Progress 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,
[Kernel-packages] [Bug 1761729] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-04-17 09:47 EDT--- Note, the logs are showing a kernel assert (BUG), not a crash. The assert is that something is wrong with the address/length being used to copy data in/out of userspace. We need to look closer at what is being done by the test suite. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761729 Title: Ubuntu 18.04 Machine crashed while running ltp. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Briggs P8 ]: Machine crashed while running ltp. ---Environment-- Kernel Build: Ubuntu 18.04 System Name : ltc-briggs2 Model/Type : P8 Platform: BML ---Uname output--- root@ltc-briggs2:~# uname -a Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Steps to reproduce-- $ git clone https://github.com/linux-test-project/ltp.git $ cd ltp $ make autotools $ ./configure $ make $ make install ltp = root@ltc-briggs2:~# root@ltc-briggs2:~# [10781.098337] LTP: starting fs_inod01 (fs_inod $TMPDIR 10 10 10) [10782.837910] LTP: starting linker01 (linktest.sh 1000 1000) [10784.504474] LTP: starting openfile01 (openfile -f10 -t10) [10784.534953] LTP: starting inode01 [10784.550767] LTP: starting inode02 [10784.739104] LTP: starting stream01 [10784.740840] LTP: starting stream02 [10784.742487] LTP: starting stream03 [10784.744532] LTP: starting stream04 [10784.746087] LTP: starting stream05 [10784.747722] LTP: starting ftest01 [10785.142054] LTP: starting ftest02 [10785.158852] LTP: starting ftest03 [10785.404760] LTP: starting ftest04 [10785.527197] LTP: starting ftest05 [10785.937164] LTP: starting ftest06 [10785.958360] LTP: starting ftest07 [10786.463382] LTP: starting ftest08 [10786.592998] LTP: starting lftest01 (lftest 100) [10786.672707] LTP: starting writetest01 (writetest) [10786.774292] LTP: starting fs_di (fs_di -d $TMPDIR) [10792.973510] LTP: starting proc01 (proc01 -m 128) [10793.865686] ICMPv6: process `proc01' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead [10795.785593] LTP: starting read_all_dev (read_all -d /dev -e '/dev/watchdog?(0)' -q -r 10) [10795.895774] NET: Registered protocol family 40 [10795.918763] Bluetooth: Core ver 2.22 [10795.918866] NET: Registered protocol family 31 [10795.918909] Bluetooth: HCI device and connection manager initialized [10795.918955] Bluetooth: HCI socket layer initialized [10795.918991] Bluetooth: L2CAP socket layer initialized [10795.919032] Bluetooth: SCO socket layer initialized [10798.374850] usercopy: kernel memory exposure attempt detected from 29431ea4 () (1023 bytes) [10798.374952] [ cut here ] [10798.374988] kernel BUG at /build/linux-2BXDjB/linux-4.15.0/mm/usercopy.c:72! [10798.375041] Oops: Exception in kernel mode, sig: 5 [#1] [10798.375080] LE SMP NR_CPUS=2048 [10871.343999650,5] OPAL: Switch to big-endian OS NUMA PowerNV [10798.375117] [10876.190849323,5] OPAL: Switch to little-endian OS Modules linked in: hci_vhci bluetooth ecdh_generic vhost_vsock cuse vmw_vsock_virtio_transport_common userio vsock uhid vhost_net vhost tap snd_seq snd_seq_device snd_timer snd soundcore binfmt_misc sctp quota_v2 quota_tree nls_iso8859_1 ntfs xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter kvm_hv kvm idt_89hpesx vmx_crypto ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd at24 powernv_rng joydev input_leds mac_hid uio_pdrv_genirq uio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss iw_cm nfs_acl lockd ib_cm grace iscsi_tcp [10798.375636] libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure scsi_transport_sas hid_generic usbhid hid ib_core qla2xxx ast i2c_algo_bit ttm mlx5_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme_fc crct10dif_vpmsum nvme_fabrics ahci mlxfw crc32c_vpmsum i40e drm devlink scsi_transport_fc megaraid_sas libahci [10798.375961] CPU: 87 PID: 4085 Comm: read_all Not tainted 4.15.0-13-generic #14-Ubuntu [10798.376013] NIP: c03c76f0 LR: c03c76ec CTR: 300378e8
[Kernel-packages] [Bug 1764752] [NEW] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0]
Public bug reported: my system often hangs, and can not be done anything ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zellkristian 1649 F pulseaudio /dev/snd/controlC0: zellkristian 1649 F pulseaudio Date: Tue Apr 17 00:51:45 2018 Failure: oops InstallationDate: Installed on 2018-04-11 (5 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) MachineType: Quanta TW9/SW9 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2009 dmi.bios.vendor: INSYDE dmi.bios.version: Q3C24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: TW9/SW9 dmi.product.version: 05 dmi.sys.vendor: Quanta ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic kernel-driver-nvidia kernel-oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764752 Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] Status in linux package in Ubuntu: Confirmed Bug description: my system often hangs, and can not be done anything ProblemType: KernelOops 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 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zellkristian 1649 F pulseaudio /dev/snd/controlC0: zellkristian 1649 F pulseaudio Date: Tue Apr 17 00:51:45 2018 Failure: oops InstallationDate: Installed on 2018-04-11 (5 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) MachineType: Quanta TW9/SW9 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=45e8aaf2-1d42-475b-bce6-df2af413f1a3 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [swapper/6:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2009 dmi.bios.vendor: INSYDE dmi.bios.version: Q3C24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrQ3C24:bd12/24/2009:svnQuanta:pnTW9/SW9:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: TW9/SW9 dmi.product.version: 05 dmi.sys.vendor: Quanta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761104 Title: fix regression in mm/hotplug, allows NVIDIA driver to work Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress 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(). == 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 1764744] [NEW] Support of freeipa-server for s390x
Public bug reported: freeipa fails to configure on s390x. (Configuration being handled by the freeipa-server-install script)This script has two failure points. The first is below: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1600634 describes a known bug but it was only resolved for x86_64. In the falling scenario the install log will have entries like the following: 2018-04-10T18:53:01Z DEBUG nsslapd-pluginenabled: 2018-04-10T18:53:01Z DEBUG on 2018-04-10T18:53:01Z DEBUG nsslapd-pluginpath: 2018-04-10T18:53:01Z DEBUG /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so 2018-04-10T18:53:01Z DEBUG nsslapd-pluginversion: 2018-04-10T18:53:01Z DEBUG 0.8 Obviously on s390x /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so will never be found. Now if I create a symbolic link with the above name that is linked to the same location but with s390x where x86_64 is located, the install will proceed past this failing location. The second failure point in the freeipa-server-install script is near the end, after the script has completed the freeipa-server-install and where it attempts to install the freeipa-client. The client install appears to fail because of a problem with certificates related to the server install. 2018-04-17T12:14:59Z ERROR Cannot connect to the server due to generic error: Insufficient access: SASL(-4): no mechanism available: No worthy mechs found (Unknown authentication method) The above appears to be related to an issue with the key database # certutil -L certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format. # ipa cert-show 1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. # ipa user-add First name: Richard >>> First name: Leading and trailing spaces are not allowed First name: Richard Last name: Young User login [ryoung]: ryoung1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-166796 severity-high targetmilestone-inin1604 ** Tags added: architecture-s39064 bugnameltc-166796 severity-high targetmilestone-inin1604 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764744 Title: Support of freeipa-server for s390x Status in linux package in Ubuntu: New Bug description: freeipa fails to configure on s390x. (Configuration being handled by the freeipa-server-install script)This script has two failure points. The first is below: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1600634 describes a known bug but it was only resolved for x86_64. In the falling scenario the install log will have entries like the following: 2018-04-10T18:53:01Z DEBUG nsslapd-pluginenabled: 2018-04-10T18:53:01Z DEBUG on 2018-04-10T18:53:01Z DEBUG nsslapd-pluginpath: 2018-04-10T18:53:01Z DEBUG /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so 2018-04-10T18:53:01Z DEBUG nsslapd-pluginversion: 2018-04-10T18:53:01Z DEBUG 0.8 Obviously on s390x /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so will never be found. Now if I create a symbolic link with the above name that is linked to the same location but with s390x where x86_64 is located, the install will proceed past this failing location. The second failure point in the freeipa-server-install script is near the end, after the script has completed the freeipa-server-install and where it attempts to install the freeipa-client. The client install appears to fail because of a problem with certificates related to the server install. 2018-04-17T12:14:59Z ERROR Cannot connect to the server due to generic error: Insufficient access: SASL(-4): no mechanism available: No worthy mechs found (Unknown authentication method) The above appears to be related to an issue with the key database # certutil -L certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format. # ipa cert-show 1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. # ipa user-add First name: Richard >>> First name: Leading and trailing spaces are not allowed First name: Richard Last name: Young User login
[Kernel-packages] [Bug 1764744] [NEW] Support of freeipa-server for s390x
You have been subscribed to a public bug: freeipa fails to configure on s390x. (Configuration being handled by the freeipa-server-install script)This script has two failure points. The first is below: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1600634 describes a known bug but it was only resolved for x86_64. In the falling scenario the install log will have entries like the following: 2018-04-10T18:53:01Z DEBUG nsslapd-pluginenabled: 2018-04-10T18:53:01Z DEBUG on 2018-04-10T18:53:01Z DEBUG nsslapd-pluginpath: 2018-04-10T18:53:01Z DEBUG /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so 2018-04-10T18:53:01Z DEBUG nsslapd-pluginversion: 2018-04-10T18:53:01Z DEBUG 0.8 Obviously on s390x /usr/lib/x86_64-linux-gnu/dirsrv/plugins/schemacompat-plugin.so will never be found. Now if I create a symbolic link with the above name that is linked to the same location but with s390x where x86_64 is located, the install will proceed past this failing location. The second failure point in the freeipa-server-install script is near the end, after the script has completed the freeipa-server-install and where it attempts to install the freeipa-client. The client install appears to fail because of a problem with certificates related to the server install. 2018-04-17T12:14:59Z ERROR Cannot connect to the server due to generic error: Insufficient access: SASL(-4): no mechanism available: No worthy mechs found (Unknown authentication method) The above appears to be related to an issue with the key database # certutil -L certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format. # ipa cert-show 1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. # ipa user-add First name: Richard >>> First name: Leading and trailing spaces are not allowed First name: Richard Last name: Young User login [ryoung]: ryoung1 ipa: ERROR: cannot connect to 'https://fipas1.pdl.pok.ibm.com/ipa/json': (SEC_ERROR_LEGACY_DATABASE) The certificate/key database is in an old, unsupported format. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-166796 severity-high targetmilestone-inin1604 -- Support of freeipa-server for s390x https://bugs.launchpad.net/bugs/1764744 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755712] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2018-04-17 08:52 EDT--- I can confirm that the testcase now works with the latest bionic snapshot: # uname -a Linux s35lp74 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:26 UTC 2018 s390x s390x s390x GNU/Linux Problem is fixed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755712 Title: Ubuntu18.04 - KVM on S390 - Multiple epoch facility bugs Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: The bionic 4.15 kernel contains KVM/s390 support for the multiple epoch facility. This code has some bugs which can result in hanging guests when running the guest on a z14 with a recent guest kernel (containing 6e2ef5e4f6cc57344762932d70d38ba4ec65fa8bs390/time: add support for the TOD clock epoch extension) The following upstream commits are necessary to fix the multi epoch facility 0e7def5fb0dc KVM: s390: provide only a single function for setting the tod (fix SCK) 1575767ef3cf KVM: s390: consider epoch index on TOD clock syncs d16b52cb9cdb KVM: s390: consider epoch index on hotplugged CPUs 5fe01793dd95 KVM: s390: take care of clock-comparator sign control As an alternative 4.15.8 also contains these fixes. ---uname output--- 4.15 ---Additional Hardware Info--- Z14 LPAR Machine Type = IBM z14 ---System Hang--- A simple test case to trigger the hang of guests: qemu-system-s390x -drive file=/data/bionic-server- s390x.iso,if=none,id=d1 -nographic -enable-kvm -device virtio-scsi-ccw -device scsi-cd,drive=d1 -m 1G -cpu z14,mepoch=on it hangs just before printing the network dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1755712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
I tried this last one, and webcam still not detected. But now syslog seems to show the 1.00 firmware. This is the output of "dmesg | grep uvcvideo": dmesg | grep uvcvideo [2.148721] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4) [2.149311] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. [2.149607] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 26). [2.149610] uvcvideo: Failed to initialize the device (-5). [2.150197] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 [2.150202] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f4) [2.150835] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. [2.151133] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 26). [2.151137] uvcvideo: Failed to initialize the device (-5). [2.151154] usbcore: registered new interface driver uvcvideo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
Ok, I use a more direct way to force the version to be 1.0: diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c index 28b91b7d756f..33ee104f1800 100644 --- a/drivers/media/usb/uvc/uvc_driver.c +++ b/drivers/media/usb/uvc/uvc_driver.c @@ -2067,6 +2067,8 @@ static int uvc_probe(struct usb_interface *intf, goto error; } + dev->uvc_version = 0x0100; + uvc_printk(KERN_INFO, "Found UVC %u.%02x device %s (%04x:%04x)\n", dev->uvc_version >> 8, dev->uvc_version & 0xff, udev->product ? udev->product : "", Here's the kernel: https://people.canonical.com/~khfeng/lp1763748-2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I built the next test kernel, up to the following commit: a0da456bbf95d2a9294799bb05c61bfb24736bb7 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1761751 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764666] Re: Xenial update to 4.4.123 stable release
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764666 Title: Xenial update to 4.4.123 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.123 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.123 stable release shall be applied: * Linux 4.4.123 * bpf: fix incorrect sign extension in check_alu_op() * usb: gadget: bdc: 64-bit pointer capability check * USB: gadget: udc: Add missing platform_device_put() on error in bdc_pci_probe() * btrfs: Fix use-after-free when cleaning up fs_devs with a single stale device * btrfs: alloc_chunk: fix DUP stripe size handling * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux * scsi: sg: only check for dxfer_len greater than 256M * scsi: sg: fix static checker warning in sg_is_valid_dxfer * scsi: sg: fix SG_DXFER_FROM_DEV transfers * irqchip/gic-v3-its: Ensure nr_ites >= nr_lpis * fs/aio: Use RCU accessors for kioctx_table->table[] * fs/aio: Add explicit RCU grace period when freeing kioctx * lock_parent() needs to recheck if dentry got __dentry_kill'ed under it * fs: Teach path_connected to handle nfs filesystems with multiple roots. * drm/amdgpu/dce: Don't turn off DP sink when disconnected * ALSA: seq: Clear client entry before deleting else at closing * ALSA: seq: Fix possible UAF in snd_seq_check_queue() * ALSA: hda - Revert power_save option default value * ALSA: pcm: Fix UAF in snd_pcm_oss_get_formats() * x86/mm: Fix vmalloc_fault to use pXd_large * x86/vm86/32: Fix POPF emulation * selftests/x86/entry_from_vm86: Add test cases for POPF * selftests/x86: Add tests for the STR and SLDT instructions * selftests/x86: Add tests for User-Mode Instruction Prevention * selftests/x86/entry_from_vm86: Exit with 1 if we fail * ima: relax requiring a file signature for new files with zero length * rcutorture/configinit: Fix build directory error message * ipvlan: add L2 check for packets arriving via virtual devices * ASoC: nuc900: Fix a loop timeout test * mac80211: remove BUG() when interface type is invalid * mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED * agp/intel: Flush all chipset writes after updating the GGTT * drm/amdkfd: Fix memory leaks in kfd topology * veth: set peer GSO values * media: cpia2: Fix a couple off by one bugs * scsi: dh: add new rdac devices * scsi: devinfo: apply to HP XP the same flags as Hitachi VSP * scsi: core: scsi_get_device_flags_keyed(): Always return device flags * spi: sun6i: disable/unprepare clocks on remove * tools/usbip: fixes build with musl libc toolchain * ath10k: fix invalid STS_CAP_OFFSET_MASK * clk: qcom: msm8916: fix mnd_width for codec_digcodec * cpufreq: Fix governor module removal race * ath10k: update tdls teardown state to target * ARM: dts: omap3-n900: Fix the audio CODEC's reset pin * ARM: dts: am335x-pepper: Fix the audio CODEC's reset pin * mtd: nand: fix interpretation of NAND_CMD_NONE in nand_command[_lp]() * net: xfrm: allow clearing socket xfrm policies. * test_firmware: fix setting old custom fw path back on exit * sched: Stop resched_cpu() from sending IPIs to offline CPUs * sched: Stop switched_to_rt() from sending IPIs to offline CPUs * ARM: dts: exynos: Correct Trats2 panel reset line * HID: elo: clear BTN_LEFT mapping * video/hdmi: Allow "empty" HDMI infoframes * drm/edid: set ELD connector type in drm_edid_to_eld() * wil6210: fix memory access violation in wil_memcpy_from/toio_32 * pwm: tegra: Increase precision in PWM rate calculation * kprobes/x86: Set kprobes pages read-only * kprobes/x86: Fix kprobe-booster not to boost far call instructions * scsi: sg: close race condition in sg_remove_sfp_usercontext() * scsi: sg: check for valid direction before starting the request * perf session: Don't rely on evlist in pipe mode * perf inject: Copy events when
[Kernel-packages] [Bug 1587674] Re: [HP Pavilion dm1-3205au Entertainment Notebook PC] Wifi intermittently connects to router on Ubuntu 16.04 LTS - Ralink RT5390
Same here. Wifi random lost connection $ lspci | grep 802.11 02:00.0 Network controller: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe on Asus X451CA Works fine on latest kernel of Kali 2017 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1587674 Title: [HP Pavilion dm1-3205au Entertainment Notebook PC] Wifi intermittently connects to router on Ubuntu 16.04 LTS - Ralink RT5390 Status in linux package in Ubuntu: Expired Bug description: The correct driver rt2800pci is installed correctly out of the box. No hardware faults. Wifi works on Ubuntu 14.04 and Windows 10. Confirmed also driver is not blocked and hardware is enabled. WORKAROUND: Assign a static IP address. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johnnel1436 F pulseaudio /dev/snd/controlC0: johnnel1436 F pulseaudio CurrentDesktop: XFCE Date: Tue May 31 18:35:18 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f7d6820f-3da5-44be-9899-a3286c944329 InstallationDate: Installed on 2016-05-20 (11 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1611 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.3A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd07/07/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr058911252B0310100:rvnHewlett-Packard:rn1611:rvr96.3A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm1 Notebook PC dmi.product.version: 058911252B0310100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU
** Changed in: linux (Ubuntu Artful) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Triaged => 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/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in intel: New 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: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1747134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764666] Re: Xenial update to 4.4.123 stable release
Skipped the following patches because they're applied already: * bpf: fix incorrect sign extension in check_alu_op() * scsi: ses: don't get power status of SES device slot on probe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764666 Title: Xenial update to 4.4.123 stable release Status in linux package in Ubuntu: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.123 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.123 stable release shall be applied: * Linux 4.4.123 * bpf: fix incorrect sign extension in check_alu_op() * usb: gadget: bdc: 64-bit pointer capability check * USB: gadget: udc: Add missing platform_device_put() on error in bdc_pci_probe() * btrfs: Fix use-after-free when cleaning up fs_devs with a single stale device * btrfs: alloc_chunk: fix DUP stripe size handling * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux * scsi: sg: only check for dxfer_len greater than 256M * scsi: sg: fix static checker warning in sg_is_valid_dxfer * scsi: sg: fix SG_DXFER_FROM_DEV transfers * irqchip/gic-v3-its: Ensure nr_ites >= nr_lpis * fs/aio: Use RCU accessors for kioctx_table->table[] * fs/aio: Add explicit RCU grace period when freeing kioctx * lock_parent() needs to recheck if dentry got __dentry_kill'ed under it * fs: Teach path_connected to handle nfs filesystems with multiple roots. * drm/amdgpu/dce: Don't turn off DP sink when disconnected * ALSA: seq: Clear client entry before deleting else at closing * ALSA: seq: Fix possible UAF in snd_seq_check_queue() * ALSA: hda - Revert power_save option default value * ALSA: pcm: Fix UAF in snd_pcm_oss_get_formats() * x86/mm: Fix vmalloc_fault to use pXd_large * x86/vm86/32: Fix POPF emulation * selftests/x86/entry_from_vm86: Add test cases for POPF * selftests/x86: Add tests for the STR and SLDT instructions * selftests/x86: Add tests for User-Mode Instruction Prevention * selftests/x86/entry_from_vm86: Exit with 1 if we fail * ima: relax requiring a file signature for new files with zero length * rcutorture/configinit: Fix build directory error message * ipvlan: add L2 check for packets arriving via virtual devices * ASoC: nuc900: Fix a loop timeout test * mac80211: remove BUG() when interface type is invalid * mac80211_hwsim: enforce PS_MANUAL_POLL to be set after PS_ENABLED * agp/intel: Flush all chipset writes after updating the GGTT * drm/amdkfd: Fix memory leaks in kfd topology * veth: set peer GSO values * media: cpia2: Fix a couple off by one bugs * scsi: dh: add new rdac devices * scsi: devinfo: apply to HP XP the same flags as Hitachi VSP * scsi: core: scsi_get_device_flags_keyed(): Always return device flags * spi: sun6i: disable/unprepare clocks on remove * tools/usbip: fixes build with musl libc toolchain * ath10k: fix invalid STS_CAP_OFFSET_MASK * clk: qcom: msm8916: fix mnd_width for codec_digcodec * cpufreq: Fix governor module removal race * ath10k: update tdls teardown state to target * ARM: dts: omap3-n900: Fix the audio CODEC's reset pin * ARM: dts: am335x-pepper: Fix the audio CODEC's reset pin * mtd: nand: fix interpretation of NAND_CMD_NONE in nand_command[_lp]() * net: xfrm: allow clearing socket xfrm policies. * test_firmware: fix setting old custom fw path back on exit * sched: Stop resched_cpu() from sending IPIs to offline CPUs * sched: Stop switched_to_rt() from sending IPIs to offline CPUs * ARM: dts: exynos: Correct Trats2 panel reset line * HID: elo: clear BTN_LEFT mapping * video/hdmi: Allow "empty" HDMI infoframes * drm/edid: set ELD connector type in drm_edid_to_eld() * wil6210: fix memory access violation in wil_memcpy_from/toio_32 * pwm: tegra: Increase precision in PWM rate calculation * kprobes/x86: Set kprobes pages read-only * kprobes/x86: Fix kprobe-booster not to boost far call instructions * scsi: sg: close race condition in sg_remove_sfp_usercontext() * scsi: sg: check for valid direction before starting the request * perf session: Don't rely on evlist in pipe mode * perf inject: Copy events when reordering events in pipe mode * drivers/perf: arm_pmu: handle no platform_device * usb:
[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2
Because, the system boot up but it stops and freezes due to problem with (nouveau) graphics. When the system is frozen it still allows me to test the brightness keys. Unfortunately with the frozen system I can not access a terminal or use it in any way. (Sorry for my painful use of the language ...) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758496 Title: Backlight does not work on a MacBookAir3,2 Status in linux package in Ubuntu: Incomplete Bug description: Backlight control does not work and there are no entries in /sys/class/backlight. When I boot my system with the option GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the brightness with the command xrandr on a terminal. I attach all the system information about this problem. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: victor 2932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 07:22:05 2018 InstallationDate: Installed on 2018-03-04 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Apple Inc. MacBookAir3,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor 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: 11/18/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA31.88Z.0061.B01.1011181342 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-942C5DF58193131B dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir3,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942C5DF58193131B dmi.modalias: dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B: dmi.product.family: MacBook dmi.product.name: MacBookAir3,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761433] Re: linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker
Cert. does not cover the ESM kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu Lin (cypressyew) -- 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/1761433 Title: linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761430 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/1761433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete
Thanks for verifying Joshua. Much appreciated! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: zfs system process hung on container stop/delete Status in Native ZFS for Linux: New Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in zfs-linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: == SRU Request [Xenial][Artful] == == Justification == It is possible to hang zfs asynchronous reads if a read to a page that is mmap'd onto the the file being read is the same offset in the mapping as in the file. This is caused by two lock operations on the page. == Fix == Upstream ZFS fix to ensure the page is not double-locked during async I/O of one or more pages. == Testing == Create a zfs pool + zfs file system, run the reproducer program in comment #28 on the zfs filesystem. Without the fix this can lock up, with the fix this runs to completion. == Regression Potential == Minimal, the locking fix addresses a fundamental bug in the locking and this should not affect ZFS read/write I/O with this fix. -- Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 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 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
[Kernel-packages] [Bug 1764690] Re: SRU: bionic: apply 50 ZFS upstream bugfixes
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764690 Title: SRU: bionic: apply 50 ZFS upstream bugfixes Status in linux package in Ubuntu: In Progress Status in zfs-linux package in Ubuntu: In Progress Bug description: SRU Justification, bionic Apply the first round of SRU bugfixes for ZFS from 0.7.5 onwards from upstream ZFS repository. This round fixes the following ZFS bugs: - OpenZFS 8373 - TXG_WAIT in ZIL commit path Closes zfsonlinux #6403 - zfs promote|rename .../%recv should be an error Closes zfsonlinux #4843, #6339 - Fix parsable 'zfs get' for compressratios Closes zfsonlinux #6436, #6449 - Fix zpool events scripted mode tab separator Closes zfsonlinux #6444, #6445 - zv_suspend_lock in zvol_open()/zvol_release() Closes zfsonlinux #6342 - Allow longer SPA names in stats, allows bigger pool names Closes zfsonlinux #6481 - vdev_mirror: load balancing fixes Closes zfsonlinux #6461 - Fix zfs_ioc_pool_sync should not use fnvlist Closes zfsonlinux #6529 - OpenZFS 8375 - Kernel memory leak in nvpair code Closes zfsonlinux #6578 - OpenZFS 7261 - nvlist code should enforce name length limit Closes zfsonlinux #6579 - OpenZFS 5778 - nvpair_type_is_array() does not recognize DATA_TYPE_INT8_ARRAY Closes zfsonlinux #6580 - dmu_objset: release bonus buffer in failure path Closes zfsonlinux #6575 - Fix false config_cache_write events Closes zfsonlinux #6617 - Fix printk() calls missing log level Closes zfsonlinux #6672 - Fix abdstats kstat on 32-bit systems Closes zfsonlinux #6721 - Relax ASSERT for #6526 Closes zfsonlinux #6526 - Fix coverity defects: 147480, 147584 (Logically dead code) Closes zfsonlinux #6745 - Fix coverity defects: CID 161388 (Resource Leak) Closes zfsonlinux #6755 - Use ashift=12 by default on SSDSC2BW48 disks Closes zfsonlinux #6774 - OpenZFS 8558, 8602 - lwp_create() returns EAGAIN Closes zfsonlinux #6779 - ZFS send fails to dump objects larger than 128PiB Closes zfsonlinux #6760 - Sort output of tunables in arc_summary.py Closes zfsonlinux #6828 - Fix data on evict_skips in arc_summary.py Closes zfsonlinux #6882, #6883 - Fix segfault in zpool iostat when adding VDEVs Closes zfsonlinux #6748, #6872 - ZTS: Fix create-o_ashift test case Closes zfsonlinux #6924, #6877 - Handle invalid options in arc_summary Closes zfsonlinux #6983 - Call commit callbacks from the tail of the list Closes zfsonlinux #6986 - Fix 'zpool add' handling of nested interior VDEVs Closes zfsonlinux #6678, #6996 - Fix -fsanitize=address memory leak kmem_alloc(0, ...) in userspace returns a leakable pointer. Closes zfsonlinux #6941 - Revert raidz_map and _col structure types Closes zfsonlinux #6981, #7023 - Use zap_count instead of cached z_size for unlink Closes zfsonlinux #7019 - OpenZFS 8897 - zpool online -e fails assertion when run on non-leaf vdevs Closes zfsonlinux #7030 - OpenZFS 8898 - creating fs with checksum=skein on the boot pools fails ungracefully Closes zfsonlinux #7031 - Emit an error message before MMP suspends pool Closes zfsonlinux #7048 - OpenZFS 8641 - "zpool clear" and "zinject" don't work on "spare" or "replacing" vdevs Closes zfsonlinux #7060 - OpenZFS 8835 - Speculative prefetch in ZFS not working for misaligned reads Closes zfsonlinux #7062 - OpenZFS 8972 - zfs holds: In scripted mode, do not pad columns with spaces Closes zfsonlinux #7063 - Revert "Remove wrong ASSERT in annotate_ecksum" Closes zfsonlinux #7079 - OpenZFS 8731 - ASSERT3U(nui64s, <=, UINT16_MAX) fails for large blocks Closes zfsonlinux #7079 - Prevent zdb(8) from occasionally hanging on I/O Closes zfsonlinux #6999 - Fix 'zfs receive -o' when used with '-e|-d' Closes zfsonlinux #7088 - Change movaps to movups in AES-NI code Closes zfsonlinux #7065, #7108 - tx_waited -> tx_dirty_delayed in trace_dmu.h Closes zfsonlinux #7096 - OpenZFS 8966 - Source file zfs_acl.c, function Closes zfsonlinux #7141 - Fix zdb -c traverse stop on damaged
[Kernel-packages] [Bug 1708130] Comment bridged from LTC Bugzilla
--- Comment From rajanikanth...@in.ibm.com 2018-04-17 06:30 EDT--- Hi Lata, We no longer have this test setup in our environment, pls close this bugzilla as un reproducible . Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708130 Title: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: == Comment: #0 - INDIRA P. JOGA- 2017-07-07 03:56:54 == Description: -- Started Leaf IO and BASE(without smt tests)and then tried to change the SMT value manually where it hangs UBUNTU BUILD: 4.10.0-26-generic Steps to re-create: -- > Installed latest Ubuntu160403 kernel on system lotkvm 4.10.0-26-generic > Leaf microcode: KMIPP113 > Started Leaf IO and BASE tests(without smt tests). root@lotkvm:/home# show.report.py HOSTNAMEKERNEL VERSION DISTRO INFO ---- lotkvm 4.10.0-26-genericUbuntu 16.04.2 LTS \n \l Current Time: Tue Jul 4 00:55:37 2017 Job-IDFOCUS Start-Time DurationFunction --- -- 1 IO 20170704-00:44:45 0.0 hr(s) 10.0 min(s) IO_Focus 2 BASE20170704-00:44:52 0.0 hr(s) 10.0 min(s) Test FOCUS IO BASESUM TOTAL 76 25 101 FAIL 0 4 4 PASS 76 21 97 (%) (100%) (84%) (96%) >Now manually changed the smt value root@lotkvm:/home# ppc64_cpu --smt SMT=8 root@lotkvm:/home# date Tue Jul 4 00:46:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=2 root@lotkvm:/home# ppc64_cpu --smt SMT=2 root@lotkvm:/home# date Tue Jul 4 00:50:01 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=4 root@lotkvm:/home# ppc64_cpu --smt SMT=4 root@lotkvm:/home# date Tue Jul 4 00:54:38 CDT 2017 root@lotkvm:/home# ppc64_cpu --smt=8 [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2055.142915] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2055.143226] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 seconds. [ 2055.143647] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 seconds. [ 2055.144029] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds. [ 2055.144353] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds. [ 2055.144665] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds. [ 2055.144936] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds. [ 2055.145195] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 seconds. [ 2175.974848] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 seconds. [ 2175.975144] Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > root@lotkvm:# ps -eaf | grep ppc* root 48054 12068 0 01:24 pts/000:00:00 grep --color=auto ppc* root 80305 5719 0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8 > ppc64_cpu --smt command
[Kernel-packages] [Bug 1760636] Re: ubuntu_blktrace_smoke_test failed with 4.4 / 4.15 kvm kernel
This issue can be reproduced in 4.15 KVM kernel as well. ** Summary changed: - ubuntu_blktrace_smoke_test failed with 4.4 Xenial kvm kernel + ubuntu_blktrace_smoke_test failed with 4.4 / 4.15 kvm kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760636 Title: ubuntu_blktrace_smoke_test failed with 4.4 / 4.15 kvm kernel Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Bug description: The test failed with: FAILED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-4.4.0-1019-kvm) FAILED (/sys/kernel/debug/tracing does not exist) Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_blktrace_smoke_test/control Output: https://pastebin.ubuntu.com/p/QY2dKcSybD/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 16:07:26 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/ubuntu/+source/linux/+bug/1760636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723914 Title: ubuntu-kvm-unit test failed with emulator test on ppc64le Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in qemu source package in Xenial: Fix Released Status in linux source package in Artful: Invalid Status in qemu source package in Artful: Fix Released Bug description: [Impact] * on start of qemu-system-ppc64 MSR_SF is not set correctly So it doesn't start 64bit as it should * Todays guests usually work around this and are fine, but it is incorrect and might be an issue down the road. Furthermore this is also a fixup to some verification tests at the same time. [Test Case] * 1. deploy xenial + HWE kernel on a ppc64el box 2. sudo apt-get install qemu-kvm -y 3. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 4. cd kvm-unit-tests 5. ./configure --endian=little; make 6. sudo ppc64_cpu --smt=off 7. sudo ./run_tests.sh -v [Regression Potential] * The changes are ppc only and provided by IBM so the potential risk is retained to the owner of the Area. Further the change is very small, so it has a very low amount of being misunderstood. [Other Info] * n/a --- Similar to bug 1723904, bug 1712803. The failed "emulator" test from kvm-unit-test will pass with qemu-2.7.1 built from source. ubuntu@modoc:~/kvm-unit-tests$ sudo /bin/bash -c "TESTNAME=emulator TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1 > " timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio -kernel powerpc/emulator.elf -smp 1 # -initrd /tmp/tmp.BJ2sE7V2Jc FAIL: emulator: 64bit: detected PASS: emulator: invalid: exception PASS: emulator: lswx: alignment PASS: emulator: lswi: alignment SUMMARY: 4 tests, 1 unexpected failures EXIT: STATUS=3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 ProcVersionSignature: User Name 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.10 Architecture: ppc64el Date: Mon Oct 16 10:10:46 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.00 0.00 0.57 1/1457 83356 ProcLocks: 1: POSIX ADVISORY WRITE 1604 00:14:19651 0 EOF 2: POSIX ADVISORY WRITE 2937 00:14:55331 0 EOF 3: FLOCK ADVISORY WRITE 3046 00:14:67623 0 EOF 4: POSIX ADVISORY WRITE 3124 00:14:57398 0 EOF 5: POSIX ADVISORY WRITE 3047 00:14:87068 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.10.0-37-generic (buildd@bos01-ppc64el-026) (gcc version 5.4.0 20160609 (User Name/IBM 5.4.0-6ubuntu1~16.04.4) ) #41~16.04.1-User Name SMP Fri Oct 6 22:44:24 UTC 2017 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1723914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
For Xenial ubuntu-deskto on Huawei server testing (UEFI), all kernel 4.4 (default) and 4.13 (hwe) and 4.15 (hwe-edge) works well (no screen blur). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in install-package package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server
** Attachment added: "screen shoot for xenial (16.04.4) with 4.15 kernel on Huawei server (UEFI)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5119225/+files/xenial-4.15-kernel-gui.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 install screen becomes blur on Huawei server Status in install-package package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in install-package source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: For all(as I know) Huawei servers, the vga adapter are embed in the iBMC chips. Those server can install from ISO manually for 16.04.4 and screen display normally. But for 18.04 ( tested both for daily and final beta)version, the install screen is blur. One of tested server is Huawei 2855 v5, the certification link for 16.04 are https://certification.ubuntu.com/hardware/201707-25596/. Below are key difference of dmesg. It seems might related with DRM. 18.04 install screen is blur dmesg ... [2.039009] fb0: EFI VGA frame buffer device ... [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.191435] [drm] No driver support for vblank timestamp query. [4.209338] checking generic (9000 30) vs hw (0 0) [4.209384] fbcon: hibmcdrmfb (fb1) is primary device [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63 ... [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on minor 0 ... [5.636624] vga16fb: initializing [5.636627] vga16fb: mapped to 0x48a7a1d2 [5.636630] checking generic (9000 30) vs hw (a 1) [5.636676] fb2: VGA16 VGA frame buffer device ... 16.04.4 install screen is fine (no screen blur) dmesg ... [2.000419] fb0: EFI VGA frame buffer device [8.795065] vga16fb: initializing [8.795068] vga16fb: mapped to 0x880a [8.795071] checking generic (9800 30) vs hw (a 1) [8.795121] fb1: VGA16 VGA frame buffer device ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764690] Re: SRU: bionic: apply 50 ZFS upstream bugfixes
** Description changed: SRU Justification, bionic Apply the first round of SRU bugfixes for ZFS from 0.7.5 onwards from upstream ZFS repository. This round fixes the following ZFS bugs: - - OpenZFS 8373 - TXG_WAIT in ZIL commit path - Closes zfsonlinux #6403 - - zfs promote|rename .../%recv should be an error - Closes zfsonlinux #4843, #6339 - - Fix parsable 'zfs get' for compressratios - Closes zfsonlinux #6436, #6449 - - Fix zpool events scripted mode tab separator - Closes zfsonlinux #6444, #6445 - - zv_suspend_lock in zvol_open()/zvol_release() - Closes zfsonlinux #6342 - - Allow longer SPA names in stats, allows bigger pool names - Closes zfsonlinux #6481 - - vdev_mirror: load balancing fixes - Closes zfsonlinux #6461 - - Fix zfs_ioc_pool_sync should not use fnvlist - Closes zfsonlinux #6529 - - OpenZFS 8375 - Kernel memory leak in nvpair code - Closes zfsonlinux #6578 - - OpenZFS 7261 - nvlist code should enforce name length limit - Closes zfsonlinux #6579 - - OpenZFS 5778 - nvpair_type_is_array() does not recognize - DATA_TYPE_INT8_ARRAY - Closes zfsonlinux #6580 - - dmu_objset: release bonus buffer in failure path - Closes zfsonlinux #6575 - - Fix false config_cache_write events - Closes zfsonlinux #6617 - - Fix printk() calls missing log level - Closes zfsonlinux #6672 - - Fix abdstats kstat on 32-bit systems - Closes zfsonlinux #6721 - - Relax ASSERT for #6526 - Closes zfsonlinux #6526 - - Fix coverity defects: 147480, 147584 (Logically dead code) - Closes zfsonlinux #6745 - - Fix coverity defects: CID 161388 (Resource Leak) - Closes zfsonlinux #6755 - - Use ashift=12 by default on SSDSC2BW48 disks - Closes zfsonlinux #6774 - - OpenZFS 8558, 8602 - lwp_create() returns EAGAIN - Closes zfsonlinux #6779 - - ZFS send fails to dump objects larger than 128PiB - Closes zfsonlinux #6760 - - Sort output of tunables in arc_summary.py - Closes zfsonlinux #6828 - - Fix data on evict_skips in arc_summary.py - Closes zfsonlinux #6882, #6883 - - Fix segfault in zpool iostat when adding VDEVs - Closes zfsonlinux #6748, #6872 - - ZTS: Fix create-o_ashift test case - Closes zfsonlinux #6924, #6877 - - Handle invalid options in arc_summary - Closes zfsonlinux #6983 - - Call commit callbacks from the tail of the list - Closes zfsonlinux #6986 - - Fix 'zpool add' handling of nested interior VDEVs - Closes zfsonlinux #6678, #6996 - - Fix -fsanitize=address memory leak - kmem_alloc(0, ...) in userspace returns a leakable pointer. - Closes zfsonlinux #6941 - - Revert raidz_map and _col structure types - Closes zfsonlinux #6981, #7023 - - Use zap_count instead of cached z_size for unlink - Closes zfsonlinux #7019 - - OpenZFS 8897 - zpool online -e fails assertion when run on non-leaf - vdevs - Closes zfsonlinux #7030 - - OpenZFS 8898 - creating fs with checksum=skein on the boot pools - fails ungracefully - Closes zfsonlinux #7031 - - Emit an error message before MMP suspends pool - Closes zfsonlinux #7048 - - OpenZFS 8641 - "zpool clear" and "zinject" don't work on "spare" - or "replacing" vdevs - Closes zfsonlinux #7060 - - OpenZFS 8835 - Speculative prefetch in ZFS not working for - misaligned reads - Closes zfsonlinux #7062 - - OpenZFS 8972 - zfs holds: In scripted mode, do not pad columns with - spaces - Closes zfsonlinux #7063 - - Revert "Remove wrong ASSERT in annotate_ecksum" - Closes zfsonlinux #7079 - - OpenZFS 8731 - ASSERT3U(nui64s, <=, UINT16_MAX) fails for large - blocks - Closes zfsonlinux #7079 - - Prevent zdb(8) from occasionally hanging on I/O - Closes zfsonlinux #6999 - - Fix 'zfs receive -o' when used with '-e|-d' - Closes zfsonlinux #7088 - - Change movaps to movups in AES-NI code - Closes zfsonlinux #7065, #7108 - - tx_waited -> tx_dirty_delayed in trace_dmu.h - Closes zfsonlinux #7096 - - OpenZFS 8966 - Source file zfs_acl.c, function - Closes zfsonlinux #7141 - - Fix zdb -c traverse stop on damaged objset root - Closes zfsonlinux #7099 - - Fix zle_decompress out of bound access - Closes zfsonlinux #7099 - - Fix racy assignment of zcb.zcb_haderrors - Closes zfsonlinux #7099 - - Fix zdb -R decompression - Closes zfsonlinux #7099, #4984 - - Fix zdb -E segfault - Closes zfsonlinux #7099 - - Fix zdb -ed on objset for exported pool - Closes zfsonlinux #7099, #6464 + - OpenZFS 8373 - TXG_WAIT in ZIL commit path + Closes zfsonlinux #6403 + - zfs promote|rename .../%recv should be an error + Closes zfsonlinux #4843, #6339 + - Fix
[Kernel-packages] [Bug 1751243] Re: ubuntu_unionmount_overlayfs_suite failed with Bionic kernel
Affecting B-KVM kernel as well (4.15.0-1004.4) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751243 Title: ubuntu_unionmount_overlayfs_suite failed with Bionic kernel Status in linux package in Ubuntu: Triaged Bug description: This issue can be found on different architectures of the Bionic kernel. Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control Result: * Command: ./run --ov Exit status: 1 Duration: 0.465664863586 stdout: *** *** ./run --ov --ts=0 open-plain *** TEST open-plain.py:10: Open O_RDONLY /mnt/a/foo100: File unexpectedly on union layer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Feb 23 09:57:36 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp