[Kernel-packages] [Bug 1761831] Re: ASUS B150M Gaming hibernate/resume failure
Please try nvidia proprietary driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops 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 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Let's wait for maintainers' reply for [1]. I Cc'ed both of you. [1] https://www.spinics.net/lists/linux-media/msg132364.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1764985] Re: test_181_config_vmap_stack failed with 4.15 KVM kernel
This issue can be found on Artful 4.13 ARM64 as well. (both moonshot and thunderX) ** Tags added: artful ** Summary changed: - test_181_config_vmap_stack failed with 4.15 KVM kernel + test_181_config_vmap_stack failed with 4.15 KVM / 4.13 ARM64 kernel -- 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/1764985 Title: test_181_config_vmap_stack failed with 4.15 KVM / 4.13 ARM64 kernel Status in QA Regression Testing: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Bug description: test_181_config_vmap_stack in ubuntu_qrt_kernel_security_test has failed with 4.15.0-1004-kvm FAIL: test_181_config_vmap_stack (__main__.KernelSecurityTest) Ensure kernel stack isolation is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2149, in test_181_config_vmap_stack self.assertEqual(self._get_config('VMAP_STACK'), expected) AssertionError: None != 'y' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Wed Apr 18 09:29:03 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1764985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765083] Re: Please cherrypick s390 unwind fix
** Changed in: ubuntu-z-systems 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/1765083 Title: Please cherrypick s390 unwind fix 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: SRU Justification Impact: On s390, an incorrect pointer being copied from the kernel to userspace breaks stack unwinding. Fix: One-line change from upstream. Only needed for 4.15+. Test Case: The glibc testsuite contains test cases, which currently fail with 4.15. Regression Potential: Minimal as this is a small, obvious bug fix for a single architecture. --- As pointed out in the glibc bug[1], there's a kernel bug preventing unwinding due to an incorrect pointer being copied to userspace. A 1-line patch[2] has been committed to Linus's tree to fix this. I investigated, and this only affects 4.15, so we only need this applied to bionic. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=22916 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b09ca746a643ca452cd41a522046a96ee5a55fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1765083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
I tried restarting thermald (1.7.0-5) at least 10 times, and the system always see the same broken sensor, the same as in 1.7.0-4 and the same as in 1.7.0-6. Perhaps by luck (or perhaps because some library or compiler version difference) thermald 1.7.0-5 worked fine on my 18.04 setup. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Fix Released Bug description: My /var/log/syslog contains a lot of "sysfs read failed /sys/class/thermal/thermal_zone4/temp". What is the problem and how to fix it (ubutuntu 18.04 / kernel 4.15.0-13-generic / thermald 1.7.0-3)? lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy thermald thermald: Installed: 1.7.0-3 Candidate: 1.7.0-3 Version table: *** 1.7.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /proc/version Linux version 4.15.0-13-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)) #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 --- ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pim1581 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413) Lsusb: Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion x360 Convertible Package: thermald 1.7.0-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=40ad8820-11eb-4e0b-8556-906bb965f2d1 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/10/2016:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Fix Released Bug description: My /var/log/syslog contains a lot of "sysfs read failed /sys/class/thermal/thermal_zone4/temp". What is the problem and how to fix it (ubutuntu 18.04 / kernel 4.15.0-13-generic / thermald 1.7.0-3)? lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy thermald thermald: Installed: 1.7.0-3 Candidate: 1.7.0-3 Version table: *** 1.7.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /proc/version Linux version 4.15.0-13-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)) #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 --- ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pim1581 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413) Lsusb: Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion x360 Convertible Package: thermald 1.7.0-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=40ad8820-11eb-4e0b-8556-906bb965f2d1 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/10/2016:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
for your records I've added the test script i use. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This occurs when tearing down an LXD container. LXD monitor process hangs with the following stack: $ sudo cat /proc/27043/stack [] msleep+0x2e/0x40 [] netdev_run_todo+0x11f/0x310 [] rtnetlink_rcv+0x2d/0x30 [] netlink_unicast+0x18c/0x240 [] netlink_sendmsg+0x2dd/0x3c0 [] sock_sendmsg+0x38/0x50 [] ___sys_sendmsg+0x2e3/0x2f0 [] __sys_sendmsg+0x54/0x90 [] SyS_sendmsg+0x12/0x20 [] do_syscall_64+0x5b/0xc0 [] entry_SYSCALL64_slow_path+0x8/0x8 [] 0x Issue submitted to LXD as well ([1]), though as indicated there, it seems to be a kernel bug. [1] https://github.com/lxc/lxd/issues/4208 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jan 31 11:42:59 2018 InstallationDate: Installed on 2016-11-09 (447 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
** Attachment added: "test script reproducing the bug on non-patched kernels." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+attachment/5123211/+files/test.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This occurs when tearing down an LXD container. LXD monitor process hangs with the following stack: $ sudo cat /proc/27043/stack [] msleep+0x2e/0x40 [] netdev_run_todo+0x11f/0x310 [] rtnetlink_rcv+0x2d/0x30 [] netlink_unicast+0x18c/0x240 [] netlink_sendmsg+0x2dd/0x3c0 [] sock_sendmsg+0x38/0x50 [] ___sys_sendmsg+0x2e3/0x2f0 [] __sys_sendmsg+0x54/0x90 [] SyS_sendmsg+0x12/0x20 [] do_syscall_64+0x5b/0xc0 [] entry_SYSCALL64_slow_path+0x8/0x8 [] 0x Issue submitted to LXD as well ([1]), though as indicated there, it seems to be a kernel bug. [1] https://github.com/lxc/lxd/issues/4208 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jan 31 11:42:59 2018 InstallationDate: Installed on 2016-11-09 (447 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
the problem also doesn't occur on the Artful test kernel. 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/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This occurs when tearing down an LXD container. LXD monitor process hangs with the following stack: $ sudo cat /proc/27043/stack [] msleep+0x2e/0x40 [] netdev_run_todo+0x11f/0x310 [] rtnetlink_rcv+0x2d/0x30 [] netlink_unicast+0x18c/0x240 [] netlink_sendmsg+0x2dd/0x3c0 [] sock_sendmsg+0x38/0x50 [] ___sys_sendmsg+0x2e3/0x2f0 [] __sys_sendmsg+0x54/0x90 [] SyS_sendmsg+0x12/0x20 [] do_syscall_64+0x5b/0xc0 [] entry_SYSCALL64_slow_path+0x8/0x8 [] 0x Issue submitted to LXD as well ([1]), though as indicated there, it seems to be a kernel bug. [1] https://github.com/lxc/lxd/issues/4208 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jan 31 11:42:59 2018 InstallationDate: Installed on 2016-11-09 (447 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761430] Re: linux: 3.13.0-145.194 -proposed tracker
Mark this task as "Fix-released", the replacement is not ready yet. ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761430 Title: linux: 3.13.0-145.194 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1761433 (linux-lts-trusty) derivatives: -- 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/1761430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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]
In light of comment #51 above, I shall pursue uploading a udev-udeb with modprobe.d config snippet that forces scsi_mod.scan=sync. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-18.04 ** Changed in: debian-installer (Ubuntu) Milestone: later => ubuntu-18.04 -- You 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: In Progress Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: In Progress 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 King srcversion: 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:
[Kernel-packages] [Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Confirmed fixed in Debian 1.7.0-6 (amd64 from incoming). Thanks, Colin. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Fix Released Bug description: My /var/log/syslog contains a lot of "sysfs read failed /sys/class/thermal/thermal_zone4/temp". What is the problem and how to fix it (ubutuntu 18.04 / kernel 4.15.0-13-generic / thermald 1.7.0-3)? lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy thermald thermald: Installed: 1.7.0-3 Candidate: 1.7.0-3 Version table: *** 1.7.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /proc/version Linux version 4.15.0-13-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)) #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 --- ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pim1581 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413) Lsusb: Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion x360 Convertible Package: thermald 1.7.0-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=40ad8820-11eb-4e0b-8556-906bb965f2d1 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/10/2016:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757573] Re: [CNL-Y] enable kernel support of graphics
File a bug in freedesktop, maybe they could provide some hints. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757573 Title: [CNL-Y] enable kernel support of graphics Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Committed Bug description: [impact] Currently in 18.04 beta1, (v4.15), CNL-Y graphics is not enabled. is_alpha_support = 1 i915/i915_pci.c 572 static const struct intel_device_info intel_cannonlake_gt2_info __initconst = { 573 GEN10_FEATURES, 574 .is_alpha_support = 1, 575 .platform = INTEL_CANNONLAKE, 576 .gen = 10, 577 .gt = 2, 578 }; Enabling it needs 59 commits backported from 4.16/drm-intel-next- queued according to a list provided by Intel. [test case] Test a kernel build with backports on CNL-Y. [regression potential] minor, they are mostly about CNL only To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1757573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765110] 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 1765110 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/1765110 Title: [regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works) Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 4.13.0-38-generic Asus UX305FA When using the 4.13.0-38-generic kernel, the login screen is completely frozen and unresponsive. Using a different kernel works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (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/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 18.04(Updated 30.03.2018) System Language: Turkish Please check screenshots --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
This bug was fixed in the package chrony - 3.2-4ubuntu4 --- chrony (3.2-4ubuntu4) bionic; urgency=medium * d/postrm: re-establish systemd-timesyncd on removal (LP: #1764357) * Notify chrony to update sources in response to systemd-networkd events (LP: #1718227) - d/links: link dispatcher script to networkd-dispatcher events routable and off - d/control: set Recommends to networkd-dispatcher - d/p/lp-1718227-ignore-non-up-down-events-in-nm-dispatcher.patch - d/p/lp-1718227-nm-dispatcher-for-networkd.patch -- Christian Ehrhardt Mon, 16 Apr 2018 17:04:06 +0200 ** Changed in: chrony (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1718227 Title: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts Status in aiccu package in Ubuntu: Invalid Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: New Status in bind9 package in Ubuntu: Invalid Status in chrony package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in controlaula package in Ubuntu: New Status in epoptes package in Ubuntu: New Status in ethtool package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in htpdate package in Ubuntu: New Status in ifenslave package in Ubuntu: Won't Fix Status in ifmetric package in Ubuntu: Won't Fix Status in ifupdown-multi package in Ubuntu: New Status in ifupdown-scripts-zg2 package in Ubuntu: Invalid Status in isatapd package in Ubuntu: New Status in lprng package in Ubuntu: New Status in miredo package in Ubuntu: New Status in mythtv package in Ubuntu: New Status in nplan package in Ubuntu: New Status in nss-pam-ldapd package in Ubuntu: New Status in ntp package in Ubuntu: New Status in openntpd package in Ubuntu: New Status in openresolv package in Ubuntu: Won't Fix Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Status in openvswitch package in Ubuntu: New Status in postfix package in Ubuntu: New Status in quicktun package in Ubuntu: New Status in resolvconf package in Ubuntu: New Status in sendmail package in Ubuntu: New Status in shorewall-init package in Ubuntu: New Status in sidedoor package in Ubuntu: New Status in slrn package in Ubuntu: New Status in tinc package in Ubuntu: New Status in ubuntu-fan package in Ubuntu: Fix Released Status in ucarp package in Ubuntu: New Status in uml-utilities package in Ubuntu: New Status in uruk package in Ubuntu: New Status in vlan package in Ubuntu: Won't Fix Status in vzctl package in Ubuntu: Triaged Status in wide-dhcpv6 package in Ubuntu: New Status in wpa package in Ubuntu: New Bug description: when network is configured with ifupdown, scripts in /etc/network/ifup.d/ were called on network being brought up and /etc/network/ifdown.d were called on network being brought down. Any packages that shipped these hooks need to be verified to have the same functionality under a netplan configured system. # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u) # for i in $binpkgs; do src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }'); [ -z "$src" ] && src="$i"; echo $src; done | sort -u aiccu aoetools avahi bind9 chrony clamav controlaula epoptes ethtool guidedog htpdate ifenslave ifmetric ifupdown-extra ifupdown-multi ifupdown-scripts-zg2 isatapd lprng miredo mythtv-backend nss-pam-ldapd ntp openntpd openresolv openssh openvpn postfix quicktun resolvconf sendmail shorewall-init sidedoor slrn tinc ubuntu-fan ucarp uml-utilities uruk vlan vzctl wide-dhcpv6 wpa Related bugs: * bug 1718227: replacement of ifupdown with netplan needs integration for /etc/network/if{up,down}.d scripts * bug 1713803: replacement of resolvconf with systemd needs integration * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: netplan (not installed) ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 19 10:53:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (789 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plan UpgradeStatus: No upgrade log present (probably fresh install) To manage not
[Kernel-packages] [Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Thanks, Colin. I will test it as soon as I can. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Fix Released Bug description: My /var/log/syslog contains a lot of "sysfs read failed /sys/class/thermal/thermal_zone4/temp". What is the problem and how to fix it (ubutuntu 18.04 / kernel 4.15.0-13-generic / thermald 1.7.0-3)? lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy thermald thermald: Installed: 1.7.0-3 Candidate: 1.7.0-3 Version table: *** 1.7.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /proc/version Linux version 4.15.0-13-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)) #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 --- ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pim1581 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413) Lsusb: Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion x360 Convertible Package: thermald 1.7.0-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=40ad8820-11eb-4e0b-8556-906bb965f2d1 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/10/2016:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765110] Re: [regression] login screen frozen after kernel update
** Summary changed: - login screen frozen after kernel update + [regression] login screen frozen after kernel update ** Tags added: regression-update ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Summary changed: - [regression] login screen frozen after kernel update + [regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765110 Title: [regression] login screen frozen after kernel update 4.13.0-38-generic (but 4.13.0-37-generic works) Status in linux package in Ubuntu: New Bug description: Ubuntu 17.10 4.13.0-38-generic Asus UX305FA When using the 4.13.0-38-generic kernel, the login screen is completely frozen and unresponsive. Using a different kernel works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
Thanks Ben for spotting the bug and for the fix, I'm uploading that to Debian right now and will sync it into Ubuntu as soon as it is ready for syncing. Much appreciated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Fix Released Bug description: My /var/log/syslog contains a lot of "sysfs read failed /sys/class/thermal/thermal_zone4/temp". What is the problem and how to fix it (ubutuntu 18.04 / kernel 4.15.0-13-generic / thermald 1.7.0-3)? lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy thermald thermald: Installed: 1.7.0-3 Candidate: 1.7.0-3 Version table: *** 1.7.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /proc/version Linux version 4.15.0-13-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)) #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 --- ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pim1581 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413) Lsusb: Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion x360 Convertible Package: thermald 1.7.0-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=40ad8820-11eb-4e0b-8556-906bb965f2d1 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/10/2016:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764320] Re: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp
@swid by "working fine!" do you just mean that the log entries are gone, or do you mean that thermald still works properly, including controlling temperature? I just reported this CRITICAL bug against 1.7.0-5 in Debian: Bug#896132: thermald uninitialised member causes loss of temperature control https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896132 The bug was introduced by the patch for the issue you reported. I have attached a patch that fixes it. ** Bug watch added: Debian Bug tracker #896132 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896132 ** Patch added: "Debian patch needed to fix the patch for this issue" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1764320/+attachment/5123166/+files/thermald-fix-uninitialised-member.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764320 Title: Thermald sysfs read failed /sys/class/thermal/thermal_zoneX/temp Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Fix Released Bug description: My /var/log/syslog contains a lot of "sysfs read failed /sys/class/thermal/thermal_zone4/temp". What is the problem and how to fix it (ubutuntu 18.04 / kernel 4.15.0-13-generic / thermald 1.7.0-3)? lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy thermald thermald: Installed: 1.7.0-3 Candidate: 1.7.0-3 Version table: *** 1.7.0-3 500 500 http://ch.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status cat /proc/version Linux version 4.15.0-13-generic (buildd@lgw01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-11ubuntu1)) #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 --- ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pim1581 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413) Lsusb: Bus 002 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion x360 Convertible Package: thermald 1.7.0-3 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=40ad8820-11eb-4e0b-8556-906bb965f2d1 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/10/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81A9 dmi.board.vendor: HP dmi.board.version: 57.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/10/2016:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn81A9:rvr57.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Kernel 282ef4729195c8503f7101d574acfb5e7c8a8209: Black screen. -- You 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 1764690] Re: SRU: bionic: apply 50 ZFS upstream bugfixes
This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu15 --- zfs-linux (0.7.5-1ubuntu15) bionic; urgency=medium * Apply and/or backport upstream bugfixes (LP: #1764690) - 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 -- Colin Ian King Tue, 17 Apr 2018 10:18:54 +0100 ** Changed in: zfs-linux (Ubuntu) Status: In Progress => 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/1764690 Title: SRU: bionic: apply 50 ZFS upstream bugfixes Status in linux package in Ubuntu: In Progress Status in z
[Kernel-packages] [Bug 1765494] 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: 1765490 + kernel-phase-changed:Thursday, 19. April 2018 22:31 UTC + kernel-phase:Packaging ** 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: 1765490 - kernel-phase-changed:Thursday, 19. April 2018 22:31 UTC - kernel-phase:Packaging + 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/1765494 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: 1765490 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1765494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen
I can confirm that kernel in artful-proposed fixed the issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen Status in intel-microcode package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in intel-microcode source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in intel-microcode source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in intel-microcode source package in Artful: Invalid Status in linux source package in Artful: Fix Committed Bug description: [Impact] * Some systems experience kernel lockups after updating to the latest intel-microcode package or when receiving updated microcode from a BIOS update. * In many cases, the lockups occur before users can reach the login screen which makes it very difficult to debug/workaround. [Test Case] * The most reliable test case currently known is to install the sssd package. Lockups may occur during package installation (disable IBPB by writing 0 to /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup will most likely occur just after booting the system up as the lock screen is displayed. [Regression Potential] * The fix is in the task switching code of the kernel so complexity of the change is relatively high. [Original Report] I don't know if this is a problem with the kernel or the microcode, but we have a significant number of computers in our organization (on both 16.04 and 17.10) that fail if they have both updated. Booting with either linux-image-4.13.0-36-generic or intel-microcode 3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to boot. ## Workaround ## 1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary avoid the problem: https://wiki.ubuntu.com/Kernel/KernelBootParameters 2. Install the previous version of package from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/14261530/+files/intel-microcode_3.20180108.0+really20170707ubuntu16.04.1_amd64.deb 3. (Optional) Hold the package so that it won't be upgraded accidentally sudo apt-mark hold intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765498] 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: 1765490 + kernel-phase-changed:Thursday, 19. April 2018 22:30 UTC + kernel-phase:Packaging ** 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: 1765490 - kernel-phase-changed:Thursday, 19. April 2018 22:30 UTC - kernel-phase:Packaging + 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/1765498 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: 1765490 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1765498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757277] Re: soft lockup from bcache leading to high load and lockup on trusty
Joseph, I'm currently testing a 4.15.0-13 kernel from xenial-16.04-edge path on these hosts. I just had the issue exhibit before the kernel change, so we should know within a couple days if that helps. Unfortunately, the logs for this system beyond those shared are not available publicly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757277 Title: soft lockup from bcache leading to high load and lockup on trusty Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: I have an environment with Dell R630 servers with RAID controllers with two virtual disks and 22 passthru devices. 2 SAS SSDs and 20 HDDs are setup in 2 bcache cachesets with a resulting 20 mounted xfs filesystems running bcache backending an 11 node swift cluster (one zone has 1 fewer nodes). Two of the zones have these nodes as described above and they appear to be exibiting soft lockups in the bcache thread of the kernel causing other kernel threads to go into i/o blocking state an keeping processes on any bcache from being successful. disk access to the virtual disks mounted with out bcache is still possible when this lockup occurs. https://pastebin.ubuntu.com/p/mtn47QqBJ3/ There are several softlockup messages found in the dmesg and many of the dumpstack are locked inside the bch_writeback_thread(); static int bch_writeback_thread(void *arg) { [...] while (!kthread_should_stop()) { down_write(&dc->writeback_lock); [...] } One coredump is found when the kswapd is doing the reclaim about the xfs inode cache. __xfs_iflock( struct xfs_inode *ip) { do { prepare_to_wait_exclusive(wq, &wait.wait, TASK_UNINTERRUPTIBLE); if (xfs_isiflocked(ip)) io_schedule(); } while (!xfs_iflock_nowait(ip)); - Possible fix commits: 1). 9baf30972b55 bcache: fix for gc and write-back race https://www.spinics.net/lists/linux-bcache/msg04713.html - Related discussions: 1). Re: [PATCH] md/bcache: Fix a deadlock while calculating writeback rate https://www.spinics.net/lists/linux-bcache/msg04617.html 2). Re: hang during suspend to RAM when bcache cache device is attached https://www.spinics.net/lists/linux-bcache/msg04636.html We are running trusty/mitaka swift storage on these nodes with 4.4.0-111 kernel (linux-image-generic-lts-xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765490] Re: linux: 4.15.0-18.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1765499 (linux-hwe-edge) derivatives: bug 1765491 (linux-raspi2), bug 1765492 (linux-oem), bug 1765494 (linux-aws), bug 1765495 (linux-azure), bug 1765497 (linux-gcp), bug 1765498 (linux-kvm) + kernel-phase:Uploaded + kernel-phase-changed:Thursday, 19. April 2018 22:02 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 1765499 (linux-hwe-edge) derivatives: bug 1765491 (linux-raspi2), bug 1765492 (linux-oem), bug 1765494 (linux-aws), bug 1765495 (linux-azure), bug 1765497 (linux-gcp), bug 1765498 (linux-kvm) kernel-phase:Uploaded kernel-phase-changed:Thursday, 19. April 2018 22:02 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/1765490 Title: linux: 4.15.0-18.19 -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: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-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 1765499 (linux-hwe-edge) derivatives: bug 1765491 (linux-raspi2), bug 1765492 (linux-oem), bug 1765494 (linux-aws), bug 1765495 (linux-azure), bug 1765497 (linux-gcp), bug 1765498 (linux-kvm) kernel-phase:Uploaded kernel-phase-changed:Thursday, 19. April 2018 22:02 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1765490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
seems to be a firmware/bios issue on the machine, not the kernel. ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1696154] Re: [18.04 FEAT] Sign POWER host/NV kernels
** Changed in: linux-signed (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1696154 Title: [18.04 FEAT] Sign POWER host/NV kernels Status in Launchpad itself: Fix Released Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-signed package in Ubuntu: Fix Committed Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765083] Re: Please cherrypick s390 unwind fix
** Also affects: linux (Ubuntu Bionic) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765083 Title: Please cherrypick s390 unwind fix Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: On s390, an incorrect pointer being copied from the kernel to userspace breaks stack unwinding. Fix: One-line change from upstream. Only needed for 4.15+. Test Case: The glibc testsuite contains test cases, which currently fail with 4.15. Regression Potential: Minimal as this is a small, obvious bug fix for a single architecture. --- As pointed out in the glibc bug[1], there's a kernel bug preventing unwinding due to an incorrect pointer being copied to userspace. A 1-line patch[2] has been committed to Linus's tree to fix this. I investigated, and this only affects 4.15, so we only need this applied to bionic. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=22916 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b09ca746a643ca452cd41a522046a96ee5a55fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1765083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764020] Re: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-sleep:25196]
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764020 Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd- sleep:25196] Status in linux package in Ubuntu: Confirmed Bug description: 18.04LTS Bionic Beaver - When the computer is set to automatic suspend the CPU gets stuck and crashes when resuming from suspend mode ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 14 22:40:12 2018 Failure: oops HibernationDevice: RESUME=UUID=d89373a2-9555-4470-a87d-d4e7103b4989 InstallationDate: Installed on 2017-05-31 (318 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: enp3s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=38efad2c-084a-48fd-b1f7-69e6095626ab 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: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-sleep:25196] UpgradeStatus: Upgraded to bionic on 2018-03-08 (37 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764020] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764020 Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd- sleep:25196] Status in linux package in Ubuntu: Confirmed Bug description: 18.04LTS Bionic Beaver - When the computer is set to automatic suspend the CPU gets stuck and crashes when resuming from suspend mode ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Sat Apr 14 22:40:12 2018 Failure: oops HibernationDevice: RESUME=UUID=d89373a2-9555-4470-a87d-d4e7103b4989 InstallationDate: Installed on 2017-05-31 (318 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: enp3s0no wireless extensions. lono wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=38efad2c-084a-48fd-b1f7-69e6095626ab 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: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [systemd-sleep:25196] UpgradeStatus: Upgraded to bionic on 2018-03-08 (37 days ago) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764020/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5
I also built an Artful test kernel with a back port of commit 510c321, which required commit 9620fef27ed2 as a prereq. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1746474/artful Can you test this kernel and see if it resolves this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746474 Title: unregister_netdevice: waiting for eth0 to become free. Usage count = 5 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: This occurs when tearing down an LXD container. LXD monitor process hangs with the following stack: $ sudo cat /proc/27043/stack [] msleep+0x2e/0x40 [] netdev_run_todo+0x11f/0x310 [] rtnetlink_rcv+0x2d/0x30 [] netlink_unicast+0x18c/0x240 [] netlink_sendmsg+0x2dd/0x3c0 [] sock_sendmsg+0x38/0x50 [] ___sys_sendmsg+0x2e3/0x2f0 [] __sys_sendmsg+0x54/0x90 [] SyS_sendmsg+0x12/0x20 [] do_syscall_64+0x5b/0xc0 [] entry_SYSCALL64_slow_path+0x8/0x8 [] 0x Issue submitted to LXD as well ([1]), though as indicated there, it seems to be a kernel bug. [1] https://github.com/lxc/lxd/issues/4208 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jan 31 11:42:59 2018 InstallationDate: Installed on 2016-11-09 (447 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
Old kernel did not work (4.13 i believe) Just installed 4.16 from the mainline builds (went with 4.16 and not 4.16.1-4.16.3 I have attached a new dmesg from the 4.16 kernel if it will help. At the end it has me replugging the cable. ** Attachment added: "dmesg-4.16-full-replug.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+attachment/5122938/+files/dmesg-4.16-full-replug.log ** Tags added: kernel-bug-exists-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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765241] Re: virtio_scsi race can corrupt memory, panic kernel
SRU Justification: Impact: This issue can cause system panics of systems using the virtio_scsi driver with the affected Ubuntu kernels. The issue manifests irregularly, as it is timing dependent. Fix: The issue is resolved by adding synchronization between the two code paths that race with one another. The most straightforward fix is to have the code wait for any outstanding requests to drain prior to freeing the target structure, e.g., --- a/drivers/scsi/virtio_scsi.c +++ b/drivers/scsi/virtio_scsi.c @@ -762,6 +762,10 @@ static int virtscsi_target_alloc(struct scsi_target *starget) static void virtscsi_target_destroy(struct scsi_target *starget) { struct virtio_scsi_target_state *tgt = starget->hostdata; + + /* we can race with concurrent virtscsi_complete_cmd */ + while (atomic_read(&tgt->reqs)) + cpu_relax(); kfree(tgt); } An alternative fix that was considered is to use a synchronize_rcu_expedited call, as that is the functionality that blocks the race in unaffected kernels. However, some call paths into virtscsi_target_destroy may hold mutexes that are not held by the upstream RCU sync calls (which enter via the block layer). For this reason the more confined fix described above was chosen. Testcase: This reproduces on Google Cloud, using the current, unmodified ubuntu-1404-lts image (with the Ubuntu 4.4 kernel). Using the two attached scripts, run e.g. ./create_shutdown_instance.sh 100 to create 100 instances. If an instance runs its startup script successfully, it'll shut itself down right away. So instances that are still running after a few minutes likely demonstrate this problem. The issue reproduces easily with n1-standard-4. create_shutdown_instance.sh: #!/bin/bash -e ZONE=us-central1-a for i in $(seq -w $1); do gcloud compute instances create shutdown-experiment-$i \ --zone="${ZONE}" \ --image-family=ubuntu-1404-lts \ --image-project=ubuntu-os-cloud \ --machine-type=n1-standard-4 \ --scopes compute-rw \ --metadata-from-file startup-script=immediate_shutdown.sh & done wait immediate_shutdown.sh: #!/bin/bash -x function get_metadata_value() { curl -H 'Metadata-Flavor: Google' \ "http://metadata.google.internal/computeMetadata/v1/instance/$1"; } readonly ZONE="$(get_metadata_value zone | awk -F'/' '{print $NF}')" gcloud compute instances delete "$(hostname)" --zone="${ZONE}" --quiet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765241 Title: virtio_scsi race can corrupt memory, panic kernel Status in linux package in Ubuntu: Confirmed Bug description: There's a race in the virtio_scsi driver (for all kernels) That race is inadvertently avoided on most kernels due to a synchronize_rcu call coincidentally placed in one of the racing code paths By happenstance, the set of patches backported to the Ubuntu 4.4 kernel ended up without a synchronize_rcu in the relevant place. The issue first manifests with commit be2a20802abbde04ae09846406d7b670731d97d2 Author: Jan Kara Date: Wed Feb 8 08:05:56 2017 +0100 block: Move bdi_unregister() to del_gendisk() BugLink: http://bugs.launchpad.net/bugs/1659111 The race can cause a kernel panic due to corruption of a freelist pointer in a slab cache. The panics occur in arbitrary places as the failure occurs at an allocation after the corruption of the pointer. However, the most common failure observed has been within virtio_scsi itself during probe processing, e.g.: [3.111628] [] kfree_const+0x22/0x30 [3.112340] [] kobject_release+0x94/0x190 [3.113126] [] kobject_put+0x27/0x50 [3.113838] [] put_device+0x17/0x20 [3.114568] [] __scsi_remove_device+0x92/0xe0 [3.115401] [] scsi_probe_and_add_lun+0x95b/0xe80 [3.116287] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [3.117227] [] ? __pm_runtime_resume+0x5b/0x80 [3.118048] [] __scsi_scan_target+0x10a/0x690 [3.118879] [] scsi_scan_channel+0x7e/0xa0 [3.119653] [] scsi_scan_host_selected+0xf3/0x160 [3.120506] [] do_scsi_scan_host+0x8d/0x90 [3.121295] [] do_scan_async+0x1c/0x190 [3.122048] [] async_run_entry_fn+0x48/0x150 [3.122846] [] process_one_work+0x165/0x480 [3.123732] [] worker_thread+0x4b/0x4d0 [3.124508] [] ? process_one_work+0x480/0x480 Details on the race: CPU A: virtscsi_probe [...] __scsi_scan_target scsi_probe_and_add_lun [on return calls __scsi_remove_device, below] scsi_probe_lun [...] blk_execute_rq blk_execute_rq waits for the completion event, and then on wakeup returns up to scsi_probe_and_all_lun, which calls __scsi_remove_device. In order for the race to occur, the wakeup must occur on a CPU other than CPU B. After being woken up by the completion of the request,
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
So booting back into the prior kernel version does not make the bug go away? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc1/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Bionic) Importance: Medium Status: Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
we really ought to fix those scripts to not do the bug tampering for devel ;) ** No longer affects: dkms (Ubuntu Bionic) ** Tags removed: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: Fix Committed Status in shim-signed package in Ubuntu: In Progress Bug description: shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765490] Re: linux: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + + backports: bug 1765499 (linux-hwe-edge) + derivatives: bug 1765491 (linux-raspi2), bug 1765492 (linux-oem), bug 1765494 (linux-aws), bug 1765495 (linux-azure), bug 1765497 (linux-gcp), bug 1765498 (linux-kvm) ** Summary changed: - linux: -proposed tracker + linux: 4.15.0-18.19 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765490 Title: linux: 4.15.0-18.19 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-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 1765499 (linux-hwe-edge) derivatives: bug 1765491 (linux-raspi2), bug 1765492 (linux-oem), bug 1765494 (linux-aws), bug 1765495 (linux-azure), bug 1765497 (linux-gcp), bug 1765498 (linux-kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1765490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Confirmed Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765494] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1765490 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-aws (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018-04-19 kernel-sru-derivative-of-1765490 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-aws (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-d2018-04-19 ** Tags added: kernel-sru-derivative-of-1765490 -- 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/1765494 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: New 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.
[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
Hello Mathieu, or anyone else affected, Accepted dkms into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: dkms (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: Fix Committed Status in shim-signed package in Ubuntu: In Progress Bug description: shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2018-04-19 14:41 EDT--- mment From xnox 2018-04-19 20:09:09 UTC--- > Can somebody please test that booting d-i with `scsi_mod.scan=sync` on the > kernel command line, on the previously affected system, makes IPR discovery > work as expected, by the time one reaches the partitioning menu without any > mitigations required from the user? I tested using this parameter as a kernel parameter, and it works as expected. I am able to see the disks as soon as I get into the disk partition tool. -- You 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: In Progress Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed 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 King srcversion: 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:v1014d034Asv000
[Kernel-packages] [Bug 1765490] [NEW] linux: 4.15.0-18.19 -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1765499 (linux-hwe-edge) derivatives: bug 1765491 (linux-raspi2), bug 1765492 (linux-oem), bug 1765494 (linux-aws), bug 1765495 (linux-azure), bug 1765497 (linux-gcp), bug 1765498 (linux-kvm) ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018-04-19 kernel-sru-master-kernel ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Tags added: kernel-sru-cycle-d2018-04-19 ** Tags added: kernel-sru-master-kernel -- You received this bug notification because you are a member of Kernel Packages, which i
[Kernel-packages] [Bug 1765496] [NEW] USB-3/PCIe Root/Thunderbolt fail to load
Public bug reported: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic ** Attachment added: "uname-a.log" https://bugs.launchpad.net/bugs/1765496/+attachment/5122902/+files/uname-a.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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Confirmed Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
** Attachment added: "dmesg-full.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+attachment/5122905/+files/dmesg-full.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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Confirmed Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+attachment/5122904/+files/version.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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Confirmed Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+attachment/5122903/+files/lspci-vvnn.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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Confirmed Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765496] Re: USB-3/PCIe Root/Thunderbolt fail to load
** Attachment added: "dmesg-replug.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+attachment/5122906/+files/dmesg-replug.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/1765496 Title: USB-3/PCIe Root/Thunderbolt fail to load Status in linux package in Ubuntu: Confirmed Bug description: I have been running 18.04 Beta fine for about a week and a half, but on Monday, after upgrading a bunch of packages and my kernel, My USB-C external monitors no longer work. They worked fine before. I tried downgrading the kernel, but that didn't change anything. I have attached a full dmesg log from boot, and a dmesg log for repluggig the usb-c cable. the PCIe Root is a Intel Sunrise and the machine is a Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765498] [NEW] linux-kvm: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1765490 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-kvm (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2018-04-19 kernel-sru-derivative-of-1765490 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-kvm (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Tags added: kernel-sru-cycle-d2018-04-19 ** Tags added: kernel-sru-derivative-of-1765490 -- 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/1765498 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: New 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.
[Kernel-packages] [Bug 1550270] Re: Touchpad stops working randomly
Same issue here, running Ubuntu 17.10 on a Lenovo Thinkpad T440. Touchpad + trackpoint move between these three states: 1) everything works fine: touch to click, touch pad, two finger scroll/right-click and trackpoint 2) everything except for two-finger actions work 3) nothing works: touchpad + trackpoint unresponsive All of this seems to happen at random. Putting the machine into suspend and waking it up again will put it in a random state of working/not working. This behavior was not observed when running 17.04 or 16.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550270 Title: Touchpad stops working randomly Status in linux package in Ubuntu: Expired Bug description: Touchpad stops working randomly, sometimes only scroll function stops working but mostly entire mouse freezes. Unable to move around the desktop. Cant find anything in dmesg-, xorg- or syslog- logs that seems to cause it. A reboot solves the problem temporarily but occures soon again so something is borked. Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Feb 26 11:31:46 2016 DistUpgraded: 2016-02-23 12:13:20,341 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978] InstallationDate: Installed on 2016-02-19 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20344 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic root=UUID=56fd75d9-c132-48f8-8cd4-e69995ecae91 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2016-02-23 (2 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Fri Feb 26 10:42:31 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 805 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8237 vendor AUO xserver.version: 2:1.17.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760377] Re: Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic
*** This bug is a duplicate of bug 1759920 *** https://bugs.launchpad.net/bugs/1759920 After downgrading to 4.13.0-36 everything worked fine for some time, then after some update the same happened under 4.13.0-36. Thankfully apt purge intel-microcode did the trick, maybe that is what got installed in my latest update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760377 Title: Ubuntu 17.10 freezes on login with kernel 4.13.0-37-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: I updated kernel to 4.13.0-37-generic, and after reboot, it freezes on the kde login screen. Even sysrq keys does not work. I rebooted again, and be able to enter password, then it freezes again on plasma loading screen. I finally selected 4.13.0-36-generic kernel from grub, and my computer booted normally. I guess there was a kernel panic, but it didn't show on screen, nor in system logs, or I cannot find it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 1 11:14:39 2018 DistUpgraded: 2017-10-02 23:05:26,340 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: kubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc 2nd Generation Core Processor Family Integrated Graphics Controller [152d:0875] NVIDIA Corporation GF106M [GeForce GT 555M] [10de:0dce] (rev a1) (prog-if 00 [VGA controller]) Subsystem: QUANTA Computer Inc GF106M [GeForce GT 555M] [152d:0875] InstallationDate: Installed on 2012-12-20 (1927 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hasee QTH6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=5e2d0528-b52e-4165-9c44-c18ef0338b43 ro quiet splash video=VGA-2:d SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-02 (180 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: SU272 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: HM65 dmi.board.vendor: Hasee dmi.board.version: TBD dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hasee dmi.chassis.version: US dmi.modalias: dmi:bvnINSYDE:bvrSU272:bd12/16/2011:svnHasee:pnQTH6:pvr03:rvnHasee:rnHM65:rvrTBD:cvnHasee:ct10:cvrUS: dmi.product.family: Intel_Mobile dmi.product.name: QTH6 dmi.product.version: 03 dmi.sys.vendor: Hasee version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Apr 1 11:07:30 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765241] Re: virtio_scsi race can corrupt memory, panic kernel
SRU Justification: Impact: This issue can cause system panics of systems using the virtio_scsi driver with the affected Ubuntu kernels. The issue manifests irregularly, as it is timing dependent. Fix: The issue is resolved by adding synchronization between the two code paths that race with one another. The lowest regression risk is to use a synchronize_rcu_expedited call, as that is the functionality that blocks the race in unaffected kernels. diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c index 03a2aad..c122e68 100644 --- a/drivers/scsi/virtio_scsi.c +++ b/drivers/scsi/virtio_scsi.c @@ -762,6 +762,9 @@ static int virtscsi_target_alloc(struct scsi_target *starget) static void virtscsi_target_destroy(struct scsi_target *starget) { struct virtio_scsi_target_state *tgt = starget->hostdata; + + /* we can race with concurrent virtscsi_complete_cmd */ + synchronize_rcu_expedited(); kfree(tgt); } It is also possible to have the code wait for any outstanding requests to drain prior to freeing the target structure, e.g., --- a/drivers/scsi/virtio_scsi.c +++ b/drivers/scsi/virtio_scsi.c @@ -762,6 +762,10 @@ static int virtscsi_target_alloc(struct scsi_target *starget) static void virtscsi_target_destroy(struct scsi_target *starget) { struct virtio_scsi_target_state *tgt = starget->hostdata; + + /* we can race with concurrent virtscsi_complete_cmd */ + while (atomic_read(&tgt->reqs)) + cpu_relax(); kfree(tgt); } This completes a bit faster for the usual case, but SCSI target destroy is not a fast path and the above runs the risk of the loop never terminating. Testcase: This reproduces on Google Cloud, using the current, unmodified ubuntu-1404-lts image (with the Ubuntu 4.4 kernel). Using the two attached scripts, run e.g. ./create_shutdown_instance.sh 100 to create 100 instances. If an instance runs its startup script successfully, it'll shut itself down right away. So instances that are still running after a few minutes likely demonstrate this problem. The issue reproduces easily with n1-standard-4. create_shutdown_instance.sh: #!/bin/bash -e ZONE=us-central1-a for i in $(seq -w $1); do gcloud compute instances create shutdown-experiment-$i \ --zone="${ZONE}" \ --image-family=ubuntu-1404-lts \ --image-project=ubuntu-os-cloud \ --machine-type=n1-standard-4 \ --scopes compute-rw \ --metadata-from-file startup-script=immediate_shutdown.sh & done wait immediate_shutdown.sh: #!/bin/bash -x function get_metadata_value() { curl -H 'Metadata-Flavor: Google' \ "http://metadata.google.internal/computeMetadata/v1/instance/$1"; } readonly ZONE="$(get_metadata_value zone | awk -F'/' '{print $NF}')" gcloud compute instances delete "$(hostname)" --zone="${ZONE}" --quiet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765241 Title: virtio_scsi race can corrupt memory, panic kernel Status in linux package in Ubuntu: Confirmed Bug description: There's a race in the virtio_scsi driver (for all kernels) That race is inadvertently avoided on most kernels due to a synchronize_rcu call coincidentally placed in one of the racing code paths By happenstance, the set of patches backported to the Ubuntu 4.4 kernel ended up without a synchronize_rcu in the relevant place. The issue first manifests with commit be2a20802abbde04ae09846406d7b670731d97d2 Author: Jan Kara Date: Wed Feb 8 08:05:56 2017 +0100 block: Move bdi_unregister() to del_gendisk() BugLink: http://bugs.launchpad.net/bugs/1659111 The race can cause a kernel panic due to corruption of a freelist pointer in a slab cache. The panics occur in arbitrary places as the failure occurs at an allocation after the corruption of the pointer. However, the most common failure observed has been within virtio_scsi itself during probe processing, e.g.: [3.111628] [] kfree_const+0x22/0x30 [3.112340] [] kobject_release+0x94/0x190 [3.113126] [] kobject_put+0x27/0x50 [3.113838] [] put_device+0x17/0x20 [3.114568] [] __scsi_remove_device+0x92/0xe0 [3.115401] [] scsi_probe_and_add_lun+0x95b/0xe80 [3.116287] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [3.117227] [] ? __pm_runtime_resume+0x5b/0x80 [3.118048] [] __scsi_scan_target+0x10a/0x690 [3.118879] [] scsi_scan_channel+0x7e/0xa0 [3.119653] [] scsi_scan_host_selected+0xf3/0x160 [3.120506] [] do_scsi_scan_host+0x8d/0x90 [3.121295] [] do_scan_async+0x1c/0x190 [3.122048] [] async_run_entry_fn+0x48/0x150 [3.122846] [] process_one_work+0x165/0x480 [3.123732] [] worker_thread+0x4b/0x4d0 [3.124508] [] ? process_one_work+0x480/0x480 Details on the race:
[Kernel-packages] [Bug 1761831] Re: ASUS B150M Gaming hibernate/resume failure
** Tags added: kernel-bug-exists-upstream ** 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops 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 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 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 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
Same problem with Linux 4.13.0-38-generic kernel under Kubuntu 18.04 beta. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765429] Re: [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
** Changed in: ubuntu-power-systems Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765429 Title: [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm) 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: ---Problem Description--- 4.15.0-17-generic #18-Ubuntu introduces newer knob to control enabling rfi_flush to mitigate meltdown/spectre which is set to disable by default for guest instead of enable. #cat /sys/kernel/debug/powerpc/rfi_flush 0 --NOK Expected: /sys/kernel/debug/powerpc/rfi_flush should be 1 bydefault if guest has the capability to mitigate. ---uname output--- Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) Machine Type = power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) ---Steps to Reproduce--- Pre-requite: FW version- power9 boston: SUPERMICRO-P9DSU-V1.10-20180413-imp (that supports mitigation) power8 tuleta: fips861/b0320a_1812.861 (that supports mitigation) Host: 4.15.0-17-generic #18-Ubuntu qemu: 1:2.11+dfsg-1ubuntu6 Guest: 4.15.0-17-generic #18-Ubuntu Results of Power9 Host: ++ 1) Boot a ubuntu 18.04 guest with latest kernel(4.15.0-17-generic #18) with pseries-bionic-sxxm machine type, it boots with "no flush" i.e /sys/kernel/debug/powerpc/rfi_flush = 0 which leads to below failure in (l1d flush - syscall) unit test for meltdown. # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2071 branches, 1006 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (132523 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 2) Once we enable rfi_flush i.e. /sys/kernel/debug/powerpc/rfi_flush = 1 manually the tests are passing fine, #echo 1 > /sys/kernel/debug/powerpc/rfi_flush # cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 1502.627548] rfi-flush: patched 9 locations (ori+mttrig type flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2074 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (196010325 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) Results of Power8 Host: +++ 1) #cat /sys/kernel/debug/powerpc/rfi_flush 0 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2066 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (150100 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) 2) #echo 1 > /sys/kernel/debug/powerpc/rfi_flush #cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0
[Kernel-packages] [Bug 1763454] Re: bpf_map_lookup_elem: BUG: unable to handle kernel paging request
** Changed in: linux (Ubuntu Xenial) Importance: Medium => High ** Changed in: linux (Ubuntu) Status: Triaged => 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/1763454 Title: bpf_map_lookup_elem: BUG: unable to handle kernel paging request Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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 [ 62.881570] [] kprobe_perf_func+0x37/0x250 [ 62.977365] [] ? finish_task_switch+0x76/0x230 [ 62.981405] [] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [ 63.092978] [
[Kernel-packages] [Bug 1764810] Re: Xenial: rfkill: fix missing return on rfkill_init
** 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/1764810 Title: Xenial: rfkill: fix missing return on rfkill_init Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: == SRU Justification == A previous backport to bug LP: #1745130 overlooked adding in an error return that was introduced by commit 6124c53edeea. Fix this by adding in the missing return. Detected by CoverityScan, CID#1467925 ("Missing return statement) Fixes: b9a5fffbaee6 ("rfkill: Add rfkill-any LED trigger") == Fix == Add missing return error code == Test == N/A == Regression Potential == Minimal, this fixes the broken backport, so the change is small and restores the original error handling behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761456] Re: linux: 4.13.0-39.44 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/artful/4.13.0-39.44 /artful-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761456 Title: linux: 4.13.0-39.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem) derivatives: bug 1761458 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761456/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762812] Re: /dev/ipmi enumeration flaky on Cavium Sabre nodes
** Changed in: linux (Ubuntu Artful) 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/1762812 Title: /dev/ipmi enumeration flaky on Cavium Sabre nodes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] There are several stability issues with the i2c-xlp9xxx that cause communication issues between the host and the BMC, leading to unpredictable results when the ipmi-ssif module tries to enumerate the device (/dev/ipmi0). [Test Case] Reboot the system several times, each time verifying that /dev/ipmi0 is present and functional (e.g. using 'sudo ipmitool lan print'). *** Note that systems need to be running firmware 6.2 or greater *** [Regression Risk] All patches are clean cherry picks from upstream, restricted to a driver that is only used on this platform in Ubuntu (also used on some MIPS platforms, for which we have no port). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765429] Re: [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765429 Title: [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: ---Problem Description--- 4.15.0-17-generic #18-Ubuntu introduces newer knob to control enabling rfi_flush to mitigate meltdown/spectre which is set to disable by default for guest instead of enable. #cat /sys/kernel/debug/powerpc/rfi_flush 0 --NOK Expected: /sys/kernel/debug/powerpc/rfi_flush should be 1 bydefault if guest has the capability to mitigate. ---uname output--- Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) Machine Type = power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) ---Steps to Reproduce--- Pre-requite: FW version- power9 boston: SUPERMICRO-P9DSU-V1.10-20180413-imp (that supports mitigation) power8 tuleta: fips861/b0320a_1812.861 (that supports mitigation) Host: 4.15.0-17-generic #18-Ubuntu qemu: 1:2.11+dfsg-1ubuntu6 Guest: 4.15.0-17-generic #18-Ubuntu Results of Power9 Host: ++ 1) Boot a ubuntu 18.04 guest with latest kernel(4.15.0-17-generic #18) with pseries-bionic-sxxm machine type, it boots with "no flush" i.e /sys/kernel/debug/powerpc/rfi_flush = 0 which leads to below failure in (l1d flush - syscall) unit test for meltdown. # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2071 branches, 1006 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (132523 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 2) Once we enable rfi_flush i.e. /sys/kernel/debug/powerpc/rfi_flush = 1 manually the tests are passing fine, #echo 1 > /sys/kernel/debug/powerpc/rfi_flush # cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 1502.627548] rfi-flush: patched 9 locations (ori+mttrig type flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2074 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (196010325 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) Results of Power8 Host: +++ 1) #cat /sys/kernel/debug/powerpc/rfi_flush 0 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2066 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (150100 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) 2) #echo 1 > /sys/kernel/debug/powerpc/rfi_flush #cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details fro
[Kernel-packages] [Bug 1763454] Re: bpf_map_lookup_elem: BUG: unable to handle kernel paging request
I was wondering about the 'Importance' definition too. It's also a panic-reboot loop just after booting when using Weave Scope in the Kubernetes cluster because Scope installs the BPF probe during initialization. -- You 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 [ 62.881570] [] kprobe_perf_func+0x37/0x250 [ 62.977365] [] ? finish_task_switch+0x76/0x230 [ 62.98140
[Kernel-packages] [Bug 1696154] Re: [18.04 FEAT] Sign POWER host/NV kernels
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1696154 Title: [18.04 FEAT] Sign POWER host/NV kernels Status in Launchpad itself: Fix Released Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux-signed package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761534] Re: "ip a" command on a guest VM shows UNKNOWN status
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761534 Title: "ip a" command on a guest VM shows UNKNOWN status Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] "ip a" command on a guest VM shows UNKNOWN status. [Test Case] * Environment : Running a guest VM with a virtio-net adaptor interface, running on DPDK. * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example: 2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 . [Regression Potential] * Regression is low, the patch fix the operstate logic for virtio when no VIRTIO_NET_F_STATUS.[1] * The patch has been first accepted in net-next, then move into Linus's git. [1] - VIRTIO_NET_F_STATUS Allow the host to inform us that the link is down by adding a VIRTIO_NET_F_STATUS which indicates that device status is available in virtio_net config. [Other Info] * Linus: https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718 * Net-next: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe [Original Description] It has been brought to our attention the following bug : Environment: The guest VM is using a canonical ubuntu image, and the eth0 is a virtio-net adaptor, running on DPDK. Background: "ip a" command relies on the operstate variable of the net_device structure maintained by the kernel. This is based on the operational state as defined in the IF MIB (RFC 2863). Device drivers are expected to update this member. But many older drivers don’t seem to be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are treated as equal, in some sense, to maintain backward compatibility. Even if we look at https://elixir.free- electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468, the function to check if interface is up, is written as follows, which says that OPER_UNKNOWN is not something to be alarmed about, and just reflective of a state that some drivers don’t care to update about. static inline bool netif_oper_up(const struct net_device *dev) { return (dev->operstate == IF_OPER_UP || dev->operstate == IF_OPER_UNKNOWN /* backward compat */); } Code Ref: 1. https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L1739 2. https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468 3. https://www.kernel.org/doc/Documentation/networking/operstates.txt Now, for traditional kernel mode network adapter drivers, this state is supposed to be manipulated by the driver. And we can safely assume that most current kernel model drivers do keep this updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764794] Re: signing: only install a signed kernel
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764794 Title: signing: only install a signed kernel Status in linux package in Ubuntu: Fix Committed 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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
@Walter Garcia-Fontes, Sorry, I missed that comment of yours. Thank you for confirming that 4.17-rc1 didn't adequately resolve the issue. I believe what this is coming down to is that there are still aspects from UVC 1.5 that are missing in the kernel then. @Kai Heng, There is no plugin currently available for fwupdmgr that can downgrade this firmware currently. -- You 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 1761104] Re: fix regression in mm/hotplug, allows NVIDIA driver to work
** Changed in: linux (Ubuntu Artful) 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/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: Fix Committed Bug description: == SRU Justification, ARTFUL == Bug fix #1747069 causes an issue for NVIDIA drivers on ppc64el platforms. According to Will Davis at NVIDIA: "- The original patch 3d79a728f9b2e6ddcce4e02c91c4de1076548a4c changed the call to arch_add_memory in mm/memory_hotplug.c to call with the boolean argument set to true instead of false, and inverted the semantics of that argument in the arch layers. - The revert patch 4fe85d5a7c50f003fe4863a1a87f5d8cc121c75c reverted the semantic change in the arch layers, but didn't revert the change to the arch_add_memory call in mm/memory_hotplug.c" And also: "It looks like the problem here is that the online_type is _MOVABLE but can_online_high_movable(nid=255) is returning false: if ((zone_idx(zone) > ZONE_NORMAL || online_type == MMOP_ONLINE_MOVABLE) && !can_online_high_movable(pfn_to_nid(pfn))) This check was removed by upstream commit 57c0a17238e22395428248c53f8e390c051c88b8, and I've verified that if I apply that commit (partially) to the 4.13.0-37.42 tree along with the previous arch_add_memory patch to make the probe work, I can fully online the GPU device memory as expected. Commit 57c0a172.. implies that the can_online_high_movable() checks weren't useful anyway, so in addition to the arch_add_memory fix, does it make sense to revert the pieces of 4fe85d5a7c50f003fe4863a1a87f5d8cc121c75c that added back the can_online_high_movable() check?" == Fix == Fix partial backport from bug #1747069, remove can_online_high_movable and fix the incorrectly set boolean argument to arch_add_memory(). == Testing == run ADT memory hotplug test, should not regress this. Without the fix, the nvidia driver on powerpc will not load because it cannot map memory for the device. With the fix it loads. == Regression Potential == This fixes a regression in the original fix and hence the regression potential is the same as the previously SRU'd bug fix for #1747069, namely: "Reverting this commit does remove some functionality, however this does not regress the kernel compared to previous releases and having a working reliable memory hotplug is the preferred option. This fix does touch some memory hotplug, so there is a risk that this may break this functionality that is not covered by the kernel regression testing." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
See this forum: https://www.dell.com/community/Linux-General/Dell-xps-13-9370-Webcam- support/td-p/6032049 Dell is downgrading the firmware by plainly substituting the whole screen with another screen that has the integrated webcam with firmware 1.00. -- You 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 1765429] Re: [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765429 Title: [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- 4.15.0-17-generic #18-Ubuntu introduces newer knob to control enabling rfi_flush to mitigate meltdown/spectre which is set to disable by default for guest instead of enable. #cat /sys/kernel/debug/powerpc/rfi_flush 0 --NOK Expected: /sys/kernel/debug/powerpc/rfi_flush should be 1 bydefault if guest has the capability to mitigate. ---uname output--- Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) Machine Type = power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) ---Steps to Reproduce--- Pre-requite: FW version- power9 boston: SUPERMICRO-P9DSU-V1.10-20180413-imp (that supports mitigation) power8 tuleta: fips861/b0320a_1812.861 (that supports mitigation) Host: 4.15.0-17-generic #18-Ubuntu qemu: 1:2.11+dfsg-1ubuntu6 Guest: 4.15.0-17-generic #18-Ubuntu Results of Power9 Host: ++ 1) Boot a ubuntu 18.04 guest with latest kernel(4.15.0-17-generic #18) with pseries-bionic-sxxm machine type, it boots with "no flush" i.e /sys/kernel/debug/powerpc/rfi_flush = 0 which leads to below failure in (l1d flush - syscall) unit test for meltdown. # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2071 branches, 1006 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (132523 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 2) Once we enable rfi_flush i.e. /sys/kernel/debug/powerpc/rfi_flush = 1 manually the tests are passing fine, #echo 1 > /sys/kernel/debug/powerpc/rfi_flush # cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 1502.627548] rfi-flush: patched 9 locations (ori+mttrig type flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2074 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (196010325 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) Results of Power8 Host: +++ 1) #cat /sys/kernel/debug/powerpc/rfi_flush 0 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2066 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (150100 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) 2) #echo 1 > /sys/kernel/debug/powerpc/rfi_flush #cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmes
[Kernel-packages] [Bug 1765153] 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/1765153 Title: Cannot open /dev/rfcommX as regular user Status in linux package in Ubuntu: Confirmed Bug description: WORKAROUND: Use sudo. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horner 3787 F pulseaudio /dev/snd/seq:timidity 1897 F timidity Date: Wed Apr 18 19:56:21 2018 HibernationDevice: RESUME=UUID=df31c7b2-5ad3-453f-93e9-db96c8ac8e2c IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=c4837fb2-0225-4050-8b25-dda5cfd4edc2 ro splash quiet splash 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.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0404 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd10/14/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
For us the importance of this issue would be High instead of Medium (not sure if there is an objective definition somewhere, could not find it). Reason is that we rely on BPF quite heavily in our infrastructure and servers just crash pretty much immediately once we install the current kernel version and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 [ 62.881570]
[Kernel-packages] [Bug 1765153] Re: Cannot open /dev/rfcommX as regular user
** Description changed: - see Bug 570692 + WORKAROUND: Use sudo. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: horner 3787 F pulseaudio - /dev/snd/seq:timidity 1897 F timidity + USERPID ACCESS COMMAND + /dev/snd/controlC0: horner 3787 F pulseaudio + /dev/snd/seq:timidity 1897 F timidity Date: Wed Apr 18 19:56:21 2018 HibernationDevice: RESUME=UUID=df31c7b2-5ad3-453f-93e9-db96c8ac8e2c IwConfig: - lono wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=c4837fb2-0225-4050-8b25-dda5cfd4edc2 ro splash quiet splash 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. + 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.4.0-45-generic N/A - linux-backports-modules-4.4.0-45-generic N/A - linux-firmware1.157.17 + linux-restricted-modules-4.4.0-45-generic N/A + linux-backports-modules-4.4.0-45-generic N/A + linux-firmware1.157.17 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0404 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd10/14/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765153 Title: Cannot open /dev/rfcommX as regular user Status in linux package in Ubuntu: Confirmed Bug description: WORKAROUND: Use sudo. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horner 3787 F pulseaudio /dev/snd/seq:timidity 1897 F timidity Date: Wed Apr 18 19:56:21 2018 HibernationDevice: RESUME=UUID=df31c7b2-5ad3-453f-93e9-db96c8ac8e2c IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=c4837fb2-0225-4050-8b25-dda5cfd4edc2 ro splash quiet splash 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.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.17 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0404 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5N7A-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.
[Kernel-packages] [Bug 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process
This bug appears to present with similar symptoms as this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232 I presume that Dell doesn't use the hpsa driver, but both are hanging at approximately the same time in the boot up process and the same subsystems appear to be involved... I would speculate that they have something in common that is triggering this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765105 Title: HP Smart Array driver fails to load, kernel panics boot process Status in linux package in Ubuntu: Confirmed Bug description: Hi I have an HP ProLiant G6 with a Smart Array controller on Bionic, Kernel 4.15.0-15, that fails to load the hpsa driver for the Smart Array, (occasionally) drops to the initramfs shell, as it cannot find a root device in a reasonable amount of time, and then finally kernel panics with the stack trace leading to the hpsa driver. Occasionally it will complain about resetting the logical volume scsi bus. Downgrading to the previous kernel 4.15.0-13 works just fine. Attached is a screenshot showing the kernel panic, and below is a link to a YouTube video of the whole boot process, a video recording from ILO. To save you the time of watching the whole thing, 39 seconds is the bus reset error, then it hangs around waiting for a root device, and the kernel panics at 4:16. The relevant information are separate below Video: https://youtu.be/45ka2Btgiqk lsb_release: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers
Re bot, the stated command can't be run because the system will not boot to a bash prompt. ** 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/1765232 Title: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers Status in linux package in Ubuntu: Confirmed Bug description: For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to 4.15.0-15. The system hangs at boot up now. Rolling back to the old kernel everything works as expected. It appears to hang while trying to enumerate an SD card device, which isn't even installed. I have tried this on a Dell R620 and R820 and both have the exact same problem. I even downloaded a new installer iso from the daily builds to reinstall the OS and the installer hangs too now. Support for Dell PowerEdge 12th gen servers appears to be broken with kernel 4.15.0-15. https://imgur.com/VT9zd0w https://imgur.com/4BQPCXo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
If the firmware is downgrade-able, I guess the best option here is to ask users to downgrade the firmware via fwupdmgr? -- You 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
I actually found the discussion [1] several days ago. The patch is to support a new format. The webcam in [1] is the UVC1.0 variant. OTOH, this bug is not about format, the error happens at driver probing. [1] https://www.spinics.net/lists/kernel/msg2755810.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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
As I say in message #5, I tried 4.17rc1 and the webcam was still not working. -- You 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 1655100] Re: NVME devices and Network devices disappears upon suspend
Any update on this for 18.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655100 Title: NVME devices and Network devices disappears upon suspend Status in linux package in Ubuntu: Triaged Status in linux source package in Yakkety: Won't Fix Bug description: Ubuntu 16.10 on a Alienware 15 R2 when resuming from suspend the NVME devices and network devices are gone. I can force the devices to re-appear issuing echo 1 > /sys/bus/pci/rescan, that was what I did to be able to submit this bug report from a live USB stick. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Mon Jan 9 17:55:50 2017 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Alienware Alienware 15 R2 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=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: Alienware dmi.bios.version: 1.3.9 dmi.board.name: 0X70NC dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.3.9:bd09/30/2016:svnAlienware:pnAlienware15R2:pvr1.3.9:rvnAlienware:rn0X70NC:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.name: Alienware 15 R2 dmi.product.version: 1.3.9 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749685] Re: Kernel panic on ThunderX
I've tried a couple memory testers: - Userspace 'memtester', which passed overnight - Kernel's 'memtest' cmdline arg, which also passed earlyboot. Running stress-ng afterwards still reported errors. Attached is the console log from the kernel 'memtest' run. Note that I saw 3 ECCs here, the last 2 do appear to be in userspace addresses: $ grep 'ECC error' console.log lundmark login: [13515.008197] Synchronous External Abort: synchronous parity or ECC error (0x8618) at 0xaaabd45d5fff [13516.695278] Synchronous External Abort: synchronous parity or ECC error (0x8618) at 0xa12d2e90 [13525.127804] Synchronous External Abort: synchronous parity or ECC error (0x8618) at 0x80007fc8 ** Attachment added: "console.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749685/+attachment/5122740/+files/console.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/1749685 Title: Kernel panic on ThunderX Status in linux package in Ubuntu: Invalid Bug description: While doing testing on lundmark, i observed (from time to time) panics on 4.13.0-32.35~16.04.1-generic - i got this one while deploying the board: Booting under MAAS direction... [ grub.cfg-40:8d:5c:ba 606B 100% 1.56KiB/s ] EFI stub: Booting Linux Kernel...[ boot-initrd 46.78MiB 100% 6.57MiB/s ] EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [0.00] Booting Linux on physical CPU 0x0 [0.00] random: get_random_bytes called from start_kernel+0x50/0x460 with crng_init=0 [0.00] Linux version 4.13.0-32-generic (buildd@bos01-arm64-018) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.5)) #35~16.04.1- Ubuntu SMP Thu Jan 25 10:10:26 UTC 2018 (Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13) [0.00] Boot CPU: AArch64 Processor [431f0a11] [0.00] Machine model: cavium,thunder-88xx [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: EFI v2.40 by American Megatrends [0.00] efi: ESRT=0x1ffce5ac18 SMBIOS 3.0=0x1ffce5a918 ACPI 2.0=0x1ffeb46000 [0.00] esrt: Reserving ESRT space from 0x001ffce5ac18 to 0x001ffce5ac50. [0.00] NUMA: NODE_DATA [mem 0x1fff0c4d00-0x1fff0c7fff] [0.00] Zone ranges: [0.00] DMA [mem 0x0050-0x] [0.00] Normal [mem 0x0001-0x001fff0f] [0.00] Movable zone start for each node [0.00] Early memory node ranges ... [0.00] Kernel command line: BOOT_IMAGE=ubuntu/arm64/hwe-16.04/xenial/daily/boot-kernel nomodeset root=squash:http://10.229.32.21:5248/images/ubu ntu/arm64/hwe-16.04/xenial/daily/squashfs ro ip=lundmark:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}e nd_cc cloud-config-url=http://10.229.32.21:5240/MAAS/metadata/latest/by-id/ttctk4/?op=get_preseed apparmor=0 log_host=10.229.32.21 log_port=514 BOOTIF=0 1-40:8d:5c:ba:cd:d4 ... [9.058541] Synchronous External Abort: synchronous parity or ECC error (0x8618) at 0x9658fc9c [9.058545] Internal error: : 8618 [#1] SMP [9.058548] Modules linked in: 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(+) i2c_thunderx(+) thunder_xcv i2c_smbus ipmi_ssif mdio_thunder thunderx_mmc mdio_ca vium ipmi_devintf ipmi_msghandler aes_neon_bs aes_neon_blk crypto_simd cryptd [9.058588] CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.13.0-32-generic #35~16.04.1-Ubuntu [9.058589] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [9.058591] task: 801f700c6900 task.stack: 801f700cc000 [9.058600] PC is at __remove_hrtimer+0x48/0xa8 [9.058602] LR is at __remove_hrtimer+0x5c/0xa8 [9.058604] pc : [] lr : [] pstate: 004001c5 [9.058606] sp : 801f79787e60 [9.058607] x29: 801f79787e60 x28: 801f700c6900 [9.058611] x27: 00021bc7a0ca x26: 08fcd000 [9.058614] x25: 0001 x24: 08fcd000 [9.058617] x23: 093b9658 x22: 801f7978f598 [9.058620] x21: 801f7978f5c0 x20: 801f7978f580 [9.058624] x19: 801f7978fa00 x18: c8e8cb78 [9.058627] x17: 668a x16: [9.058630] x15: 968adcc0 x14: 343030302c333030 [9.058633] x13: 302c323030302c31 x12: 3030302c30303030 [9.058636] x11: c635fa10 x10: 0b00 [9.058639] x9 : 0040 x8 : 801f780026f0 [9.058643] x7 :
[Kernel-packages] [Bug 1761433] Re: linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker
ESM kernels are not covered by ADT tests. Setting automated-testing to 'Invalid'. ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/automated-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 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 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]
So my current feelings about this are as follows: udev-udeb should ship /lib/modprobe.d/ directory It should contain systemd.conf, just like the deb udev package, which sets bonding max_bonds=0 and dummy numdummies=0. It should also contain scsi-scan-sync.conf that that sets `options scsi_mod scan=sync` This way, when hw-detect runs `update-dev` and `update-dev --settle` all the scsi module loading will be blocking said sync points correctly, using the scsi kernel built-in scan timeouts etc. Potentially no disks found menu, needs an option to "Rescan all SCSI drives again". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] Status in The Ubuntu-power-systems project: In Progress Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed 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 King srcversion: 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*
[Kernel-packages] [Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]
Can somebody please test that booting d-i with `scsi_mod.scan=sync` on the kernel command line, on the previously affected system, makes IPR discovery work as expected, by the time one reaches the partitioning menu without any mitigations required from the user? -- You 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: In Progress Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed 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 King srcversion: 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:v1014d034Asv
[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
@Kai Heng, I believe this should help: Can you please apply https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/media/usb/uvc?h=v4.17-rc1&id=e96cdc9a0aa2fcaa276a76e8ffa86fc10a1d3d99 to a test kernel? Or alternatively can someone affected please test 4.17-rc1 (it's included)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765232 Title: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers Status in linux package in Ubuntu: Incomplete Bug description: For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to 4.15.0-15. The system hangs at boot up now. Rolling back to the old kernel everything works as expected. It appears to hang while trying to enumerate an SD card device, which isn't even installed. I have tried this on a Dell R620 and R820 and both have the exact same problem. I even downloaded a new installer iso from the daily builds to reinstall the OS and the installer hangs too now. Support for Dell PowerEdge 12th gen servers appears to be broken with kernel 4.15.0-15. https://imgur.com/VT9zd0w https://imgur.com/4BQPCXo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: 282ef4729195c8503f7101d574acfb5e7c8a8209 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 1705466] Re: Kernel oopsed when booting
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Artful) Status: Confirmed => 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/1705466 Title: Kernel oopsed when booting Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Invalid Bug description: Spoke to Leann and she suggested that I log this. Artful running proposed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-11-generic 4.11.0-11.16 ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10 Uname: Linux 4.11.0-11-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1870 F pulseaudio CurrentDesktop: GNOME Date: Thu Jul 20 13:14:48 2017 InstallationDate: Installed on 2017-07-10 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709) MachineType: Dell Inc. Inspiron 11-3168 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic.efi.signed root=UUID=02673bea-6091-48ee-8a1f-44d3ea4b71ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-11-generic N/A linux-backports-modules-4.11.0-11-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0XKKP9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd03/24/2016:svnDellInc.:pnInspiron11-3168:pvr1.0.1:rvnDellInc.:rn0XKKP9:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 11-3168 dmi.product.version: 1.0.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765429] [NEW] [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
Public bug reported: ---Problem Description--- 4.15.0-17-generic #18-Ubuntu introduces newer knob to control enabling rfi_flush to mitigate meltdown/spectre which is set to disable by default for guest instead of enable. #cat /sys/kernel/debug/powerpc/rfi_flush 0 --NOK Expected: /sys/kernel/debug/powerpc/rfi_flush should be 1 bydefault if guest has the capability to mitigate. ---uname output--- Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) Machine Type = power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) ---Steps to Reproduce--- Pre-requite: FW version- power9 boston: SUPERMICRO-P9DSU-V1.10-20180413-imp (that supports mitigation) power8 tuleta: fips861/b0320a_1812.861 (that supports mitigation) Host: 4.15.0-17-generic #18-Ubuntu qemu: 1:2.11+dfsg-1ubuntu6 Guest: 4.15.0-17-generic #18-Ubuntu Results of Power9 Host: ++ 1) Boot a ubuntu 18.04 guest with latest kernel(4.15.0-17-generic #18) with pseries-bionic-sxxm machine type, it boots with "no flush" i.e /sys/kernel/debug/powerpc/rfi_flush = 0 which leads to below failure in (l1d flush - syscall) unit test for meltdown. # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2071 branches, 1006 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (132523 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 2) Once we enable rfi_flush i.e. /sys/kernel/debug/powerpc/rfi_flush = 1 manually the tests are passing fine, #echo 1 > /sys/kernel/debug/powerpc/rfi_flush # cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 1502.627548] rfi-flush: patched 9 locations (ori+mttrig type flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2074 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (196010325 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) Results of Power8 Host: +++ 1) #cat /sys/kernel/debug/powerpc/rfi_flush 0 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2066 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (150100 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) 2) #echo 1 > /sys/kernel/debug/powerpc/rfi_flush #cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 243.736201] rfi-flush: patched 9 locations (fallback displacement flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2054 branches, 1008 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (195105463 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux == Breno Leitao == Patch sent to the mailing list already: https://lists.ubuntu.com/archives/k
[Kernel-packages] [Bug 1765429] [NEW] [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel: meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
You have been subscribed to a public bug: ---Problem Description--- 4.15.0-17-generic #18-Ubuntu introduces newer knob to control enabling rfi_flush to mitigate meltdown/spectre which is set to disable by default for guest instead of enable. #cat /sys/kernel/debug/powerpc/rfi_flush 0 --NOK Expected: /sys/kernel/debug/powerpc/rfi_flush should be 1 bydefault if guest has the capability to mitigate. ---uname output--- Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) Machine Type = power9 boston 2.2 (pvr 004e 1202), power8 tuleta 2.1 (pvr 004b 0201) ---Steps to Reproduce--- Pre-requite: FW version- power9 boston: SUPERMICRO-P9DSU-V1.10-20180413-imp (that supports mitigation) power8 tuleta: fips861/b0320a_1812.861 (that supports mitigation) Host: 4.15.0-17-generic #18-Ubuntu qemu: 1:2.11+dfsg-1ubuntu6 Guest: 4.15.0-17-generic #18-Ubuntu Results of Power9 Host: ++ 1) Boot a ubuntu 18.04 guest with latest kernel(4.15.0-17-generic #18) with pseries-bionic-sxxm machine type, it boots with "no flush" i.e /sys/kernel/debug/powerpc/rfi_flush = 0 which leads to below failure in (l1d flush - syscall) unit test for meltdown. # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2071 branches, 1006 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (132523 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux 2) Once we enable rfi_flush i.e. /sys/kernel/debug/powerpc/rfi_flush = 1 manually the tests are passing fine, #echo 1 > /sys/kernel/debug/powerpc/rfi_flush # cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: ori type flush available [0.00] rfi-flush: mttrig type flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 1502.627548] rfi-flush: patched 9 locations (ori+mttrig type flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2074 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (196010325 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) Results of Power8 Host: +++ 1) #cat /sys/kernel/debug/powerpc/rfi_flush 0 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2066 branches, 1010 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... FAIL (150100 misses, 19200 expected) [10/10 failures] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) 2) #echo 1 > /sys/kernel/debug/powerpc/rfi_flush #cat /sys/kernel/debug/powerpc/rfi_flush 1 # make tests = Machine details from dmesg: dmesg | grep -e 'pSeries machine' -e 'OPAL detected' -e rfi-fixups -e rfi-flush [0.00] Using pSeries machine description [0.00] rfi-flush: fallback displacement flush available [0.00] rfi-flush: patched 9 locations (no flush) [ 243.736201] rfi-flush: patched 9 locations (fallback displacement flush) = Running tests... Testing mitigation for spectre (ii. indirect branch prediction)... PASS (2054 branches, 1008 branch misses) Testing mitigation for meltdown (l1d flush - syscall)... PASS (195105463 misses, 19200 expected) [10/10 pass] Testing mitigation for meltdown (l1d flush - userspace)... SKIP (!power8) # uname -a Linux ubuntu 4.15.0-17-generic #18-Ubuntu SMP Mon Apr 16 21:16:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux == Breno Leitao == Patch sent to the mailing list already: https://lists.
[Kernel-packages] [Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute
Same problem under Kubuntu 18.04 beta (Linux 4.15.0-15-generic) with an ASUS H81M-C motherboard: [2.812149] clocksource: Switched to clocksource tsc [ 34.133640] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) But "tpm_tis.force=1" seems to have no effect... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1308264 Title: Ubuntu 14.04 Beta 2 stuck at "Switched to clocksource tsc" when booting up, then resumes booting to the login screen, after 1 minute Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 Beta 2 (Final Beta), it takes remarkebly long to boot up into Ubuntu. Ubuntu gets stuck at "Switched to clocksource tsc" for a almost 1 minute or longer, then it resumes booting up to the login screen. On Ubuntu 13.10 it only takes about 7 seconds to get to the login screen, while it takes almost more than a minute to get on the login screen on Ubuntu 14.04 Beta 2. I hope this issue could be fixed. I have the Acer C720 (chromebook) that has been enabled to use legacy boot so I can use other OS's. Other Acer C720 users have been faceing the same problem also. Video of Boot https://www.youtube.com/watch?v=PVkFTsEzS80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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]
Two things. SCSI_SCAN_ASYNC=y is set from xenial to bionic. If we believe this is what is causing the race here, we can try booting d-i with a kernel parameter 'scsi_mod.scan=sync' specified. (or i can rebuild d-i with such kernel cmdline built-in if required). And check if that helps to resolve this case. I do wonder, if d-i should be taking the control of the scan itself, meaning, booting with scsi_mod.scan=none and doing `echo "- - -" > /sys/class/scsi_host/*/scan` at the appropriate stage of disk-detect. Or if we do async scan, trigger a rescan at disk-detect stage. `echo 1 > /sys/class/scsi_device/device/rescan` Will be checking the disk-detect / scsi code, to see if it does trigger scans, and if it correctly blocks on said scans to complete. -- You 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: In Progress Status in debian-installer package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed 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 King srcversion: 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:v10
[Kernel-packages] [Bug 1748983] Re: Generate per-machine MOK for dkms signing
I'm uploading things now; let's keep them blocked in proposed just long enough that I have the time for one last test before it reaches everyone. ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1748983 Title: Generate per-machine MOK for dkms signing Status in dkms package in Ubuntu: In Progress Status in shim-signed package in Ubuntu: In Progress Bug description: shim-signed's update-secureboot-policy should allow creating a machine-owner key, and using this for signing kernel modules built via DKMS. Key generation and enrolling should be made as easy as possible for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1748983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761430] Re: linux: 3.13.0-145.194 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-145.194 /trusty-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761430 Title: linux: 3.13.0-145.194 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1761433 (linux-lts-trusty) derivatives: -- 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/1761430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic
*** This bug is a duplicate of bug 1736116 *** https://bugs.launchpad.net/bugs/1736116 If you change the value of GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to "" Ubuntu will boot. When it hangs during boot you can press left Shift key during boot - in the boot menu press "e" and remove the values quiet splash (at the end of the file pre last line). THen Ctrl-X and Ubuntu will boot. Then you have to modify the parameter GRUB_CMDLINE_LINUX_DEFAULT to "" in /etc/default/grub and do an sudo update-grub afterwards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748901 Title: System hang with Virtualbox & kernel 4.13.0-32-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Opinion Bug description: Some (maybe all) kernels in the 4.13.0 series are hanging with Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a Virtualbox VM, the VM's window appears, clears to black, and then the mouse freezes. I do NOT see any BIOS/EFI information or boot loader in the VM; the hang occurs before those messages appear. (I've tried this with the VM set for both BIOS and EFI booting with no difference.) The host computer also stops responding to pings or anything else; the only solution seems to be to do a cold reset. I've tested this on a different computer running the same kernel and the latest Ubuntu 18.04 alpha and had no problems there. Here's some data from the affected computer: $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ cat /proc/version_signature Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 $ dpkg -s virtualbox | grep Version Version: 5.0.40-dfsg-0ubuntu1.16.04.2 This problem does NOT occur with earlier kernels, such as those in the 4.4.0 series. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rodsmith 2661 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2014-05-02 (1382 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro root=/dev/mapper/hostname-trusty_crypt quiet splash initrd=\initrd.img-4.13.0-32-generic ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago) UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AFZ.015.161206.KS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP740U5M-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 740U5M dmi.product.version: P02AFZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765110] Re: login screen frozen after kernel update
Updated description. ** Description changed: Ubuntu 17.10 - 4.13.0-37-generic + 4.13.0-38-generic Asus UX305FA When using the 4.13.0-37-generic kernel, the login screen is completely frozen and unresponsive. Using a different kernel works fine. ** Description changed: Ubuntu 17.10 4.13.0-38-generic Asus UX305FA - When using the 4.13.0-37-generic kernel, the login screen is completely frozen and unresponsive. + When using the 4.13.0-38-generic kernel, the login screen is completely frozen and unresponsive. Using a different kernel works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765110 Title: login screen frozen after kernel update Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 4.13.0-38-generic Asus UX305FA When using the 4.13.0-38-generic kernel, the login screen is completely frozen and unresponsive. Using a different kernel works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762413] Re: Memory corruption detected in low memory
Tested the 4.16.3 vanilla kernel, with quite the same errors ** Attachment added: "4.16.3-vanilla" https://bugs.launchpad.net/ubuntu/bionic/+source/linux/+bug/1762413/+attachment/5122627/+files/4.16.3-vanilla ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu Bionic) 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/1762413 Title: Memory corruption detected in low memory Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: That laptop (intel PIV) was running xenial (kernel 4.4) without problem. Now that the bionic upgrade have been done (kernel 4.15), journalctl -b have logged: kernel: Memory corruption detected in low memory kernel: WARNING: CPU: 0 PID: 32 at /build/linux-QWz1wR/linux-4.15.0/arch/x86/kernel/check.c:142 check_for_bios_corruption+0x8c/0xc0 kernel: Modules linked in: kernel: CPU: 0 PID: 32 Comm: kworker/0:1 Not tainted 4.15.0-15-generic #16-Ubuntu kernel: Hardware name: MEDION M296M/, BIOS NOTE BIOS Version/L2850100 11/14/2002 kernel: Workqueue: events check_corruption kernel: EIP: check_for_bios_corruption+0x8c/0xc0 kernel: EFLAGS: 00210296 CPU: 0 kernel: EAX: 0028 EBX: c001 ECX: 0198 EDX: kernel: ESI: EDI: cde1f2b0 EBP: f5477f30 ESP: f5477f1c kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 kernel: CR0: 80050033 CR2: CR3: 0de0f000 CR4: 06f0 kernel: Call Trace: kernel: TCP: Hash tables configured (established 8192 bind 8192) kernel: UDP hash table entries: 512 (order: 2, 16384 bytes) kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) kernel: NET: Registered protocol family 1 kernel: ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 5 kernel: PCI: setting IRQ 5 as level-triggered kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5 kernel: ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 5 kernel: pci :00:03.3: enabling device ( -> 0002) kernel: ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5 kernel: pci :01:00.0: Video device with shadowed ROM at [mem 0x000c-0x000d] kernel: PCI: CLS 16 bytes, default 64 kernel: Unpacking initramfs... kernel: Freeing initrd memory: 48800K kernel: Scanning for low memory corruption every 60 seconds kernel: Corrupted low memory at f11b93a5 (4e14 phys) = 1039 kernel: Corrupted low memory at aa7e680c (4e18 phys) = 2217 kernel: Corrupted low memory at 07d67f4e (4e1c phys) = 0600 kernel: Corrupted low memory at 14e58341 (4e20 phys) = 00802000 kernel: Corrupted low memory at 177ce42b (4e24 phys) = d000 kernel: Corrupted low memory at a4c6d47a (4e48 phys) = 00c0 kernel: Corrupted low memory at ab7c4974 (4e64 phys) = 837009fe kernel: Corrupted low memory at 5d1625c4 (4e68 phys) = 00b71303 kernel: Corrupted low memory at 86bf688b (4e6c phys) = 50082502 kernel: Corrupted low memory at 78519e78 (4e70 phys) = 0b32d512 kernel: Corrupted low memory at cefe909f (4e74 phys) = 6f6f kernel: Corrupted low memory at efb2e08f (4e78 phys) = 801a0003 kernel: Corrupted low memory at c5b91a0b (4e7c phys) = 00e98001 kernel: Corrupted low memory at 662c373b (4e80 phys) = 004f kernel: Corrupted low memory at 5ff6a218 (4e84 phys) = 00309e3f kernel: Corrupted low memory at b1b63dbd (4e88 phys) = 0062 kernel: Corrupted low memory at bc8cc516 (4e90 phys) = 0012 kernel: Corrupted low memory at be02ab1d (4e94 phys) = 00302622 kernel: Corrupted low memory at 92c91e75 (4e98 phys) = 0b800085 kernel: Corrupted low memory at fd16c7d0 (4e9c phys) = 01000c20 kernel: Corrupted low memory at 068765bf (4ea0 phys) = 8004 kernel: Corrupted low memory at 6500aa34 (4ea8 phys) = 0160 kernel: Corrupted low memory at 2dffebb8 (4eac phys) = 10741600 kernel: Corrupted low memory at f4e7c54d (4eb0 phys) = 1000 kernel: Corrupted low memory at bdecb33f (4eb4 phys) = c233d4c2 kernel: Corrupted low memory at c259f3aa (4eb8 phys) = 77010303 kernel: Corrupted low memory at ded7243b (4ebc phys) = c2005000 kernel: Corrupted low memory at 60e188a8 (4ec0 phys) = 08000142 kernel: Corrupted low memory at d446d5b1 (4ec4 phys) = 1000 kernel: Corrupted low memory at a39f733b (4ec8 phys) = 4f00 kernel: Corrupted low memory at ecda55e9 (4ecc phys) = 30304fee kernel: Corrupted low memory at e5fee885 (4ed0 phys) = 8500 kernel: Corrupted low memory at f1a141fa (4ed4 phys) = 0022 kernel: Corrupted low memory at 70088389 (4ed8 phys) = 1f000207 kernel: Corrupted low memory at f61ca70e (4ee4 phys) = 06334222 kernel: Corrupted low memory at d031d304 (4ee8 phys) = 0149 kernel: Corrupted low memory at abbcf68b (4eec phys) = 00aa kernel
[Kernel-packages] [Bug 1765380] Re: busybox sh preseed/late_command
** Also affects: busybox (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu) ** Summary changed: - busybox sh preseed/late_command + Bionic: busybox sh preseed/late_command ** Tags added: netinstall ** Description changed: - 1) lsb_release -rd + 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 - 2) apt-cache policy busybox - busybox: - Installed: 1:1.27.2-2ubuntu3 + 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ + initrd.gz 2018-04-18 09:13 45M + linux 2018-04-18 09:13 7.9M 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox - syslog: + syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? ** Description changed: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ initrd.gz 2018-04-18 09:13 45M linux 2018-04-18 09:13 7.9M - 3+4) preseed installation on Bionic, late_command almost the same in - Xenial and there is working + busybox: + Installed: 1:1.27.2-2ubuntu3 + + + 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1765380 Title: Bionic: busybox sh preseed/late_command Status in busybox package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/ initrd.gz 2018-04-18 09:13 45M linux 2018-04-18 09:13 7.9M busybox: Installed: 1:1.27.2-2ubuntu3 3+4) preseed installation on Bionic, late_command almost the same in Xenial and there is working preseed.cfg d-i preseed/late_command string /tmp/late_command ls -l /bin/sh lrwxrwxrwx 1 root root 4 Sep 26 2014 /bin/sh -> busybox syslog: running: /tmp/late_command nothing happend on shell: /tmp/late_command head late_commaand #!/bin/sh printf '' > /usr/lib/finish-install.d/55netcfg-copy-config; in-target mkdir -p /opt/MegaRAID/MegaCli/; in-target mkdir -p /root/.ssh; in-target mkdir /etc/check_mk; So is there a bug in busybox sh? How can I debug busybox sh script.sh? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1765380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765373] Re: nfp: flower: fixes for cmesg processing timeouts
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765373 Title: nfp: flower: fixes for cmesg processing timeouts Status in linux package in Ubuntu: Incomplete Bug description: This is a backport request from Netronome for Ubuntu 18.04 LTS This patch-set improves MTU handling for flower offload on Netronome SmartNICs. The max MTU is correctly capped and physical port MTU is communicated to the FW (and indirectly HW). This prevents the driver from incorrectly reporting a larger MTU than the HW is configured to handle. The upstream commits, accepted for v4.17, are: 29a5dcae2790 ("nfp: flower: offload phys port MTU change") 167cebeffadd ("nfp: modify app MTU setting callbacks") There are also a dependencies on: ccbdc596f4f6 ("nfp: bpf: don't allow changing MTU above BPF offload limit when active") b57b62139e53 ("nfp: flower: read extra feature support from fw") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1765379] Re: nfp: flower: fixes for cmesg processing timeouts
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765379 Title: nfp: flower: fixes for cmesg processing timeouts Status in linux package in Ubuntu: Incomplete Bug description: This is a backport request from Netronome for Ubuntu 18.04 LTS This patch-set improves control message handling making it more robust with respect to timeouts caused by excessively large number of messages queued for processing in a workqueue. The upstream commits, accepted for v4.16, are: cf2cbadc20f5 ("nfp: flower: split and limit cmsg skb lists") 0b1a989ef5a7 ("nfp: flower: move route ack control messages out of the workqueue") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744510] Re: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in
1) Just tested bionic, same behavior. 2) I also discovered something new about this issue when I tested this on bionic. I _thought_ I observed this on artful, but I wasn't certain so I didn't mention it, but now I'm certain. Immediately after reboot, when I move the mouse (note I'm using Xorg, not Wayland), the mouse pointer on the screen moves for a fraction of a second and _then_ stops working at until I unplug the dongle and plug it back in again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744510 Title: RF mouse (with USB dongle) doesn't work after reboot until I unplug it and plug it back in Status in linux package in Ubuntu: Confirmed Bug description: My wireless mouse doesn't work after I reboot until I unplug its USB dongle and plug it back in. I don't see anything in Xorg.0.log which obviously explains this problem. It looks like the mouse is added to the X server configuration on startup without any problems, at least unless I'm misreading the log, and then the second time it's added, when I unplug it and plug it back in, it looks like the same thing happens in the log, but then the mouse works. This was a problem in 17.04 as well, i.e., it isn't new in 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 20 18:31:15 2018 DistUpgraded: 2018-01-20 12:11:24,767 ERROR Cache can not be locked (E:Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable), E:Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?) DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1131] InstallationDate: Installed on 2016-01-16 (735 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Predator G6-710 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2018-01-20 (0 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jan 20 17:16:47 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Again, I test the 4.16 kernel with the parameter "nomodese". As Kaihengfeng guessed the system boot but the problem still there; /sys/class/backlight folder was empty. My second test was boot again with 4.16 without "nomodeset" parameter in the grub file and the results were others. As I expected the system was frozen and in this last test the brightness keys didn't work. It smells like a problem betwen my firmware and the kernel. I can do more test to find the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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