[Kernel-packages] [Bug 1782207] Re: KVM SnowRidge Processor Trace v4
Feature request that does not need the kernel logs the bot asks for ** 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/1782207 Title: KVM SnowRidge Processor Trace v4 Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: The PEBS(Processor Event Based Sampling) facility allows software to profile workload behavior by periodically capturing machine state, memory access information and other groups of architectural information. In native systems, PEBS uses a debug store mechanism to store a set of architectural state information for the processor and we need to specify a linear pages for the output buffer which must be pinned to physical pages. In virtualized systems, pinning the platform physical pages for the output buffer is difficult. PT V4 provide a method to format PEBS sampling data to new type of trace packet and output to Intel Processor Trace buffer. This depend on PT-VMX(Enabling use of EPT to redirect PT output)which enabled in ICX platform. Need modify in KVM and Qemu. Intel Processor Trace v4 task list: ◾PT VMX which is done and in upstream phase, and need more review and update effort ◾PEBS via PT on SNR. It's new added task, which target to ww48 ◾PT PEBS/EMON integration. This feature allows PEBS data to be written into PT output channel, leveraging PT Virtualization work for PEBS. ◾cpuid support and context switch ◾Support host-guest mode and system mode More Open feature includes Live Migration support and LBR support Upstream target 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731408] Re: [Feature] [HMEM] Move device-dax resource reservation to be per-instance
** No longer affects: linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags removed: intel-kernel-19.04 ** Tags added: intel-kernel-19.10 ** Description changed: Description Stop reserving an entire dax-region and let individual instances hold the reservation for their range. Target Kernel: 5.1 - Target Release: 19.04 + Target Release: 19.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/1731408 Title: [Feature] [HMEM] Move device-dax resource reservation to be per- instance Status in intel: Fix Committed Status in linux package in Ubuntu: New Bug description: Description Stop reserving an entire dax-region and let individual instances hold the reservation for their range. Target Kernel: 5.1 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1731408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730883] Re: [HMEM] Allow persistent memory to be used like normal RAM
** No longer affects: linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730883 Title: [HMEM] Allow persistent memory to be used like normal RAM Status in intel: Fix Committed Status in linux package in Ubuntu: New Bug description: Description Persistent memory is cool. But, currently, you have to rewrite your applications to use it. Wouldn't it be cool if you could just have it show up in your system like normal RAM and get to it like a slow blob of memory? Well... have I got the patch series for you! This series adds a new "driver" to which pmem devices can be attached. Once attached, the memory "owned" by the device is hot-added to the kernel and managed like any other memory. On systems with an HMAT (a new ACPI table), each socket (roughly) will have a separate NUMA node for its persistent memory so this newly-added memory can be selected by its unique NUMA node. Target Kernel: 5.1 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782208] Re: KVM SnowRidge Adaptive PEBS
Feature request that does not need the kernel logs the bot asks for ** 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/1782208 Title: KVM SnowRidge Adaptive PEBS Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: With the addition of more CPU state information of data, the PEBS(Processor Event Based Sampling) record size is greatly increased. However, most general users of PEBS require just the eventingIP and do not require such a large PEBS record. Adaptive PEBS provides Software the capability to configure the PEBS records to capture only the data of interest, keeping the record size compact. Need modify KVM and Qemu. Adaptive PEBS (Processor Event Based Sampling) is configurable PEBS records for only interested data collection from massive PEBS data. It depends on PEBS via PT. The enabling work includes: ◾Expose this feature and MSR configure bit in guest PEBS driver ◾Save and restore status in vCPU when vm_exit and vm_entry ◾Support both host-guest mode and system mode. Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824520] Re: Unable to turn off the airplane mode with wireless key on Dell M3800
This is fixed in Disco. Cosmic needs to be fixed though. ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824520 Title: Unable to turn off the airplane mode with wireless key on Dell M3800 Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Cosmic: New Bug description: The airplane mode can be activated with the wireless key combination on this laptop (fn + PrtScn) You will see the "Airplane mode enabled" notification, and the BT / Wireless turned off accordingly. However the same key combination cannot turn the wireless back on. You will see the "Airplane mode disabled" notification followed by the "Airplane mode enabled" message. It feels a bit like a repeat-key issue. But the evtest shows the identical result: * Turn on the airplane mode: Event: time 1555070280.383302, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070280.383302, -- SYN_REPORT Event: time 1555070280.383327, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070280.383327, -- SYN_REPORT * Turn off the airplane mode: Event: time 1555070325.562502, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 1 Event: time 1555070325.562502, -- SYN_REPORT Event: time 1555070325.562514, type 1 (EV_KEY), code 247 (KEY_RFKILL), value 0 Event: time 1555070325.562514, -- SYN_REPORT dmesg for turning on the airplane mode: Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 12 08:03:53 u-Dell-Precision-M3800 kernel: [ 1229.634982] wlp6s0: deauthenticating from 18:9c:5d:31:3f:e0 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4574] manager: rfkill: WiFi now disabled by radio killswitch Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4581] device (wlp6s0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed') Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): canceled DHCP transaction, DHCP client pid 6521 Apr 12 08:03:53 u-Dell-Precision-M3800 NetworkManager[968]: [1555070633.4590] dhcp4 (wlp6s0): state changed bound -> done Apr 12 08:03:53 u-Dell-Precision-M3800 systemd[1]: Started Load/Save RF Kill Switch Status. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=18:9c:5d:31:3f:e0 reason=3 locally_generated=1 Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv6 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::bb23:69c3:d7b9:f6df. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Interface wlp6s0.IPv4 no longer relevant for mDNS. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 10.101.46.102. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for fe80::bb23:69c3:d7b9:f6df on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 avahi-daemon[974]: Withdrawing address record for 10.101.46.102 on wlp6s0. Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] offline Apr 12 08:03:53 u-Dell-Precision-M3800 wpa_supplicant[951]: rfkill: WLAN soft blocked Apr 12 08:03:53 u-Dell-Precision-M3800 whoopsie[1976]: [08:03:53] Cannot reach: https://daisy.ubuntu.com Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using nameserver 127.0.0.53#53 Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: reading /etc/resolv.conf Apr 12 08:03:53 u-Dell-Precision-M3800 dnsmasq[1424]: using
[Kernel-packages] [Bug 1782208] Re: KVM SnowRidge Adaptive PEBS
Are there updates and/or references to commits in those projects already that we can use to track and integrate those features? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782208 Title: KVM SnowRidge Adaptive PEBS Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: With the addition of more CPU state information of data, the PEBS(Processor Event Based Sampling) record size is greatly increased. However, most general users of PEBS require just the eventingIP and do not require such a large PEBS record. Adaptive PEBS provides Software the capability to configure the PEBS records to capture only the data of interest, keeping the record size compact. Need modify KVM and Qemu. Adaptive PEBS (Processor Event Based Sampling) is configurable PEBS records for only interested data collection from massive PEBS data. It depends on PEBS via PT. The enabling work includes: ◾Expose this feature and MSR configure bit in guest PEBS driver ◾Save and restore status in vCPU when vm_exit and vm_entry ◾Support both host-guest mode and system mode. Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782207] Re: KVM SnowRidge Processor Trace v4
@Quanxian - as usual let us know when you have mailing list posts or even better commits in the kernel and qemu that we can use to track and integrate 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/1782207 Title: KVM SnowRidge Processor Trace v4 Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: The PEBS(Processor Event Based Sampling) facility allows software to profile workload behavior by periodically capturing machine state, memory access information and other groups of architectural information. In native systems, PEBS uses a debug store mechanism to store a set of architectural state information for the processor and we need to specify a linear pages for the output buffer which must be pinned to physical pages. In virtualized systems, pinning the platform physical pages for the output buffer is difficult. PT V4 provide a method to format PEBS sampling data to new type of trace packet and output to Intel Processor Trace buffer. This depend on PT-VMX(Enabling use of EPT to redirect PT output)which enabled in ICX platform. Need modify in KVM and Qemu. Intel Processor Trace v4 task list: ◾PT VMX which is done and in upstream phase, and need more review and update effort ◾PEBS via PT on SNR. It's new added task, which target to ww48 ◾PT PEBS/EMON integration. This feature allows PEBS data to be written into PT output channel, leveraging PT Virtualization work for PEBS. ◾cpuid support and context switch ◾Support host-guest mode and system mode More Open feature includes Live Migration support and LBR support Upstream target 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782208] 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 1782208 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782208 Title: KVM SnowRidge Adaptive PEBS Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: With the addition of more CPU state information of data, the PEBS(Processor Event Based Sampling) record size is greatly increased. However, most general users of PEBS require just the eventingIP and do not require such a large PEBS record. Adaptive PEBS provides Software the capability to configure the PEBS records to capture only the data of interest, keeping the record size compact. Need modify KVM and Qemu. Adaptive PEBS (Processor Event Based Sampling) is configurable PEBS records for only interested data collection from massive PEBS data. It depends on PEBS via PT. The enabling work includes: ◾Expose this feature and MSR configure bit in guest PEBS driver ◾Save and restore status in vCPU when vm_exit and vm_entry ◾Support both host-guest mode and system mode. Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782207] 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 1782207 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782207 Title: KVM SnowRidge Processor Trace v4 Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: The PEBS(Processor Event Based Sampling) facility allows software to profile workload behavior by periodically capturing machine state, memory access information and other groups of architectural information. In native systems, PEBS uses a debug store mechanism to store a set of architectural state information for the processor and we need to specify a linear pages for the output buffer which must be pinned to physical pages. In virtualized systems, pinning the platform physical pages for the output buffer is difficult. PT V4 provide a method to format PEBS sampling data to new type of trace packet and output to Intel Processor Trace buffer. This depend on PT-VMX(Enabling use of EPT to redirect PT output)which enabled in ICX platform. Need modify in KVM and Qemu. Intel Processor Trace v4 task list: ◾PT VMX which is done and in upstream phase, and need more review and update effort ◾PEBS via PT on SNR. It's new added task, which target to ww48 ◾PT PEBS/EMON integration. This feature allows PEBS data to be written into PT output channel, leveraging PT Virtualization work for PEBS. ◾cpuid support and context switch ◾Support host-guest mode and system mode More Open feature includes Live Migration support and LBR support Upstream target 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782207] Re: KVM SnowRidge Processor Trace v4
This is another bug filed against xen, but then mentioning qemu and kernel. There was no feedback since my question a few months ago, but xen as the only target package makes no sense it seems. I added bug tasks accordingly. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782207 Title: KVM SnowRidge Processor Trace v4 Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: The PEBS(Processor Event Based Sampling) facility allows software to profile workload behavior by periodically capturing machine state, memory access information and other groups of architectural information. In native systems, PEBS uses a debug store mechanism to store a set of architectural state information for the processor and we need to specify a linear pages for the output buffer which must be pinned to physical pages. In virtualized systems, pinning the platform physical pages for the output buffer is difficult. PT V4 provide a method to format PEBS sampling data to new type of trace packet and output to Intel Processor Trace buffer. This depend on PT-VMX(Enabling use of EPT to redirect PT output)which enabled in ICX platform. Need modify in KVM and Qemu. Intel Processor Trace v4 task list: ◾PT VMX which is done and in upstream phase, and need more review and update effort ◾PEBS via PT on SNR. It's new added task, which target to ww48 ◾PT PEBS/EMON integration. This feature allows PEBS data to be written into PT output channel, leveraging PT Virtualization work for PEBS. ◾cpuid support and context switch ◾Support host-guest mode and system mode More Open feature includes Live Migration support and LBR support Upstream target 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782208] Re: KVM SnowRidge Adaptive PEBS
Again, this semes to be a Kernel/qemu bug that was only filed against xen. Added bug tasks to not get lost. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782208 Title: KVM SnowRidge Adaptive PEBS Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Bug description: With the addition of more CPU state information of data, the PEBS(Processor Event Based Sampling) record size is greatly increased. However, most general users of PEBS require just the eventingIP and do not require such a large PEBS record. Adaptive PEBS provides Software the capability to configure the PEBS records to capture only the data of interest, keeping the record size compact. Need modify KVM and Qemu. Adaptive PEBS (Processor Event Based Sampling) is configurable PEBS records for only interested data collection from massive PEBS data. It depends on PEBS via PT. The enabling work includes: ◾Expose this feature and MSR configure bit in guest PEBS driver ◾Save and restore status in vCPU when vm_exit and vm_entry ◾Support both host-guest mode and system mode. Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)
The qemu commits have landed in 4.0 - so that part should work in Ubuntu 19.10 The kernel commits are in 5.1 as outlined by Paul above already (thanks). @Paul - since the initial upstream target was "linux 5.3" are there things missing or did this just work out faster than expected? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782206 Title: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Triaged Status in xen package in Ubuntu: Incomplete Bug description: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 5.3/Qemu-3.10 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
** Tags added: oem-priority ** Changed in: oem-priority Importance: Undecided => High -- 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/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable
Hi, I have not seen the kernel changes in 5.2 RCs - is there an update on their progress? Also any updates, links, commits on the related qemu contribution? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782209 Title: KVM SnowRidge Split-lock disable Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: When bit 29 is set in Test Control MSR register 0x33, a #AC execption is generated for split locked accesses at all CPL irrespective of CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK assertion. Then developers can reconstruct their program accordingly Upstream target linux 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
There are couple of OEM images requires this fix and expected to be released next week. Can we expect the linux-firmware including this fix updated before May 15th, if possible? -- 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/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826358] Re: linux: 4.15.0-49.53 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe) derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), bug 1826348 (linux-oracle), bug 1826350 (linux-fips), bug 1827353 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 29. April 2019 16:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826358 Title: linux: 4.15.0-49.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe) derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), bug 1826348 (linux-oracle), bug 1826350 (linux-fips), bug 1827353 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 29. April 2019 16:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM
Failed with 10 minutes timeout setting as well. -- 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/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815733] Re: unnecessary request_queue freeze
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1815733 Title: unnecessary request_queue freeze Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Invalid Bug description: Hi all, In linux-4.15, which is used as hwe-edge in xenial, there's an unexpected behavior. It results in latency spikes of generic_make_request() function call. How to reproduce: 1. Run fio: fio --name=test --rw=randwrite --direct=1 --filename=/dev/sdt --iodepth=1 --fsync=1 --ioengine=libaio --write_lat_log loglat 2. While fio is writing to the device, change nr_requests setting to the same value as current: echo 256 > /sys/block/sdt/queue/nr_requests or: if scheduler is already none: echo none > /sys/block/sdt/queue/scheduler 3. Stop fio and check slat log: ... 3980, 16, 1, 4096 3999, 17, 1, 4096 4010, 19, 1, 4096 4020, 18, 1, 4096 4045, 10821, 1, 4096 4054, 25, 1, 4096 4070, 12, 1, 4096 4083, 17, 1, 4096 4094, 16, 1, 4096 4111, 17, 1, 4096 ... There're a few patches to fix this behavior: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.1/block=e5fa81408fb43ebabde65938ef8b20ae879017e7 https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=for-5.1/block=fbd72127c975dc8e532ecc73d52f3b1b00935bec This behavior affects production systems, because every change uevent triggers udev to change settings prior to udev rules. Some software, for example arcconf (tool for managing adaptec HBA adapters) triggers uevents for every block device. So, every call to arcconf utility results in latency spike. Could this be backported to 4.15 kernel for xenial/bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812805] Re: powerpc/pmu/ebb test in ubuntu_kernel_selftest failed with "error while loading shared libraries" on Bionic/Cosmic PowerPC
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812805 Title: powerpc/pmu/ebb test in ubuntu_kernel_selftest failed with "error while loading shared libraries" on Bionic/Cosmic PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == Justification == The selftests/powerpc/pmu/ebb test will fail on Ubunut PowerPC with: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0f046fb04550 for symbol `' out of range This is because the Ubuntu toolchain builds has PIE enabled by default. == Fix == 98415da0 (selftests/powerpc/pmu: Link ebb tests with -no-pie) This fix will use -no-pie flag to build the test. Patch already landed in Disco, and can be cherry-picked for B/C. For Xenial, we don't have this test in our tree thus it can be ignored. == Test == Patch verified on a Bionic P9 system, all the ebb tests will pass. == Regression Potential == None. This patchset is just for the kernel testing tool. == Original Bug Report == In linux/tools/testing/selftests/powerpc/pmu/ebb: selftests: reg_access_test ./reg_access_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0e3dcc384550 for symbol `' out of range not ok 1..1 selftests: reg_access_test [FAIL] selftests: event_attributes_test ./event_attributes_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x059efa3c4af0 for symbol `' out of range not ok 1..2 selftests: event_attributes_test [FAIL] selftests: cycles_test ./cycles_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0baa1a664750 for symbol `' out of range not ok 1..3 selftests: cycles_test [FAIL] selftests: cycles_with_freeze_test ./cycles_with_freeze_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x03b22e124920 for symbol `' out of range not ok 1..4 selftests: cycles_with_freeze_test [FAIL] selftests: pmc56_overflow_test ./pmc56_overflow_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0a07e9bb47e0 for symbol `' out of range not ok 1..5 selftests: pmc56_overflow_test [FAIL] selftests: ebb_vs_cpu_event_test ./ebb_vs_cpu_event_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x01b0f3644820 for symbol `' out of range not ok 1..6 selftests: ebb_vs_cpu_event_test [FAIL] selftests: cpu_event_vs_ebb_test ./cpu_event_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0ac0538147e0 for symbol `' out of range not ok 1..7 selftests: cpu_event_vs_ebb_test [FAIL] selftests: cpu_event_pinned_vs_ebb_test ./cpu_event_pinned_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0d1eaeab4800 for symbol `' out of range not ok 1..8 selftests: cpu_event_pinned_vs_ebb_test [FAIL] selftests: task_event_vs_ebb_test ./task_event_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x034ed21e4730 for symbol `' out of range not ok 1..9 selftests: task_event_vs_ebb_test [FAIL] selftests: task_event_pinned_vs_ebb_test ./task_event_pinned_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0a5b9a844780 for symbol `' out of range not ok 1..10 selftests: task_event_pinned_vs_ebb_test [FAIL] selftests: multi_ebb_procs_test ./multi_ebb_procs_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x08b649fb4870 for symbol `' out of range not ok 1..11 selftests: multi_ebb_procs_test [FAIL] selftests: multi_counter_test ./multi_counter_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x063184dc4970 for symbol `' out of range not ok 1..12 selftests: multi_counter_test [FAIL] selftests: pmae_handling_test ./pmae_handling_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0e62316248d0 for symbol `' out of range not ok 1..13
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM
Failed with 10 minutes timeout setting as well. -- 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/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1644804] Re: [Vostro 15-3568] Right key does not work on this clickpad
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644804 Title: [Vostro 15-3568] Right key does not work on this clickpad Status in HWE Next: Invalid Status in linux package in Ubuntu: Expired Bug description: CID: 201606-22528 Dell Vostro 15-3568 The right key on the clickpad does not work on this laptop. Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot and test the right key Result: * Not working at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1525 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 06:52:56 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1644804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep Status in linux package in Ubuntu: Expired Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 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.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825780] Re: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825780 Title: Kprobe event string type argument failed in ftrace from ubuntu_kernel_selftests on B/C i386 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: == Justification == When running the ftrace in ubunut_kernel_selftests, the "Kprobe event string type argument" test will fail on Bionic / Cosmic i386: [22] Kprobe event string type argument [FAIL] This is because the test was trying to probe a notrace function. # grep create_trace_kprobe /sys/kernel/debug/tracing/available_filter_functions == Fix == 6fc7c411 (selftests/ftrace: Fix kprobe string testcase to not probe notrace function) This will change the event to trace in the test, from create_trace_kprobe to tracefs_create_dir Patch can be cherry-picked for Cosmic. For Bionic and Xenial, it can be cherry-picked after the commit 9855c462 for bug 1812809. Although we don't run this ftrace test in Xenial, it will still be a plus to fix this. It's already been applied in D. This patch belongs to a patchset [1], in which further limits kprobe- events probing on notrace function. To address this issue for the testing tool this one will be suffice. [1] https://lkml.org/lkml/2018/7/30/257 == Test == Patch tested with Bionic / Cosmic i386. Test passed as expected: [22] Kprobe event string type argument [PASS] == Regression potential == None. This patch is just for the kernel testing tool. == Original bug report == Failure spotted on Bionic / Cosmic i386 (node fozzie) [22] Kprobe event string type argument [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Snapshot and tracing setting [PASS] [6] event tracing - enable/disable with event level files[PASS] [7] event tracing - restricts events based on pid[PASS] [8] event tracing - enable/disable with subsystem level files[PASS] [9] event tracing - enable/disable with top level files [PASS] [10] ftrace - function graph filters with stack tracer [PASS] [11] ftrace - function graph filters [PASS] [12] ftrace - function pid filters [PASS] [13] ftrace - test for function event triggers [PASS] [14] ftrace - function profiler with function tracing[PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances [PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument [FAIL] [23] Kprobe event argument syntax[PASS] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer [PASS] [27] Kretprobe dynamic event with arguments [PASS] [28] Kretprobe dynamic event with maxactive [PASS] [29] Register/unregister many kprobe events [PASS] [30] event trigger - test extended error support [PASS] [31] event trigger - test field variable support [PASS] [32] event trigger - test multiple actions on hist trigger [PASS] [33] event trigger - test inter-event histogram trigger onmatch action [PASS] [34] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [35] event trigger - test inter-event histogram trigger onmax action [PASS] [36] event trigger - test synthetic_events syntax parser [PASS] [37] event trigger - test event enable/disable trigger [PASS] [38] event trigger - test trigger filter [PASS] [39] event trigger - test histogram modifiers[PASS] [40] event trigger - test multiple histogram triggers[PASS] [41] event trigger - test snapshot-trigger [PASS] [42] event trigger - test stacktrace-trigger [PASS] [43] trace_marker trigger - test snapshot trigger[PASS] [44] trace_marker trigger - test
[Kernel-packages] [Bug 1826343] Re: linux-kvm: 4.15.0-1033.33 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Signoff phase-changed: Thursday, 02. May 2019 10:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1826343 Title: linux-kvm: 4.15.0-1033.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Signoff phase-changed: Thursday, 02. May 2019 10:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826343] Re: linux-kvm: 4.15.0-1033.33 -proposed tracker
4.15.0-1033.33 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel (bug 1763323) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) psock_tpacket in net failed (bug 1812176) RTNETLINK in net (bug 1812194) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) user_copy in user (bug 1812198) ftrace (bug 1812318) ubuntu_kvm_unit_tests - apic-split (bug 1821390) apic timeouted (bug 1748103) eventinj (bug 1827977) port80 (bug 1748105) pcid (bug 1827979) vmx (bug 1821394) ept (bug 1824228) vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) vmx_apic_passthrough_thread (bug 1822309) hyperv_synic (bug 1827980) hyperv_stimer (bug 1827982) ubuntu_ltp - fork failed on some test cases due to Resource temporarily unavailable ubuntu_ltp_syscalls - acct01 skipped (bug 1824794) inotify08 (bug 1775784) fanotify09 case 2 (bug 1804594) msgstress03 (bug 1797341) msgstress04 (bug 1797348) quotactl01, quotactl02, quotactl03 (bug 1797325) sync_file_range02 (bug 1819116) ubuntu_lxc - network issue for lxc-test-no-new-privs (bug 1821152) ubuntu_qrt_kernel_security - SCHED_STACK_END_CHECK should be enabled (bug 1812159) LOCK_DOWN_KERNEL should be enabled (bug 1811981) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ubuntu_sysdig_smoke_test - Unable to insert sysdig_probe module on B-KVM kernel (bug 1766565) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1826343 Title: linux-kvm: 4.15.0-1033.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Signoff phase-changed: Thursday, 02. May 2019 10:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827982] [NEW] hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM
Public bug reported: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Test timeouted. # TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826358] Re: linux: 4.15.0-49.53 -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/bionic/4.15.0-49.53 /bionic-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/1826358 Title: linux: 4.15.0-49.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826354 (xenial/linux-azure), bug 1826357 (xenial/linux-hwe) derivatives: bug 1826334 (linux-raspi2), bug 1826335 (linux-snapdragon), bug 1826336 (linux-oem), bug 1826338 (linux-aws), bug 1826340 (linux-gcp), bug 1826342 (linux-gke-4.15), bug 1826343 (linux-kvm), bug 1826345 (linux-ibm-gt), bug 1826348 (linux-oracle), bug 1826350 (linux-fips), bug 1827353 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Monday, 29. April 2019 16:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827978] 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 1827978 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827978 Title: [SGX]Flexible Launch Control Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Implement open source launch enclave and bundle it with the Linux kernel so that the kernel can generate launch tokens for enclaves that the user requests to run. Flexible Launch Control consists of: Enclave singing tool for kbuild (DONE) Launch Enclave and its user space (DONE) Host program for the LE that reads SIGSTRUCT instances from stdin and outputs them to stdout (DONE) Kbuild changes to generate LE signing key (IN PROGRESS) Driver changes to launch lehost using user space helper framework (IN PROGRESS) Kernel changes to link lehost to vmlinux (IN PROGRESS) Relevant URLs: Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le Kernel tree: https://github.com/jsakkine-intel/linux-sgx Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1827978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730885] 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 1730885 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730885 Title: [Feature] SGX mainline enabling Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description Umbrella task for SGX mainline kernel features. Target Kernel: 5.4 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801260] Re: USB Type-C Alternate Mode support
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801260 Title: USB Type-C Alternate Mode support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description Let's track here the progress for generic alternate mode support. The discovery and entering/exiting the modes is common for all alternate modes, and the USB PD code will handle that. The tasks currently related to this task are: 1) The alternate modes will need custom control that we don't want to mix into the generic USB PD code. For example the DP altmode defines custom VDM (Vendor Defined Message) for "configure" and "status" commands. So we will need to create somekind of API for Alternate Mode "drivers". 2) The Alternate Modes need to keep the underlying components and drivers informed about their status, possibly even allow some control. For example, with DP altmode the graphics side will need to know the cable orientation and the number of lanes (the modes define the pin configuration in DP altmode, so the numer of available lanes as well AFAIK). So we need API for this. *) UCSI may need some special attention, as with UCSI we don't handle the USB PD communication. We just get the status of the port. But we will know which alternate mode has been enterred, and we can actually request enter/exit a mode even with UCSI. But we don't know for example the cable orientation. Commits: 0e3bb7d6894d9b6e67d6382bb03a46a1dc989588 49cbb33dfdeb7651b91c2316a61b644d8e6cfe22 4ab8c18d4d67321cc7b660559de17511d4fc0237 8a37d87d72f0c69f837229c04d2fcd7117ea57e7 93dd2112c7b2fa5512cc4aff2c449420487fcb68 e9576fe8e605c4413beb91b290b8a473985710de Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801263] Re: Update to the latest QAT driver
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801263 Title: Update to the latest QAT driver Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Update to the latest QAT driver Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827980] [NEW] hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM
Public bug reported: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM Status in linux-kvm package in Ubuntu: New Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1827980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760755] 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 1760755 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760755 Title: Intel FPGA Phase 1 driver upstream Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description: The FPGA upstream driver Phase 1 includes the FPGA driver framework and minimum function support with basic function can work, end users can write apps, image can be flushed and programed. The driver includes below modules: PCIe driver core FME driver core with PR support AFU driver core with DMA + region mmap support Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1760755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730885] Re: [Feature] SGX mainline enabling
** Also affects: ubuntu Importance: Undecided Status: New ** Package changed: ubuntu => linux (Ubuntu) ** Description changed: Description Umbrella task for SGX mainline kernel features. Target Kernel: 5.4 - Target Release: 19.04 + Target Release: 19.10 ** Tags removed: intel-kernel-19.04 ** Tags added: intel-kernel-19.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/1730885 Title: [Feature] SGX mainline enabling Status in intel: Triaged Status in linux package in Ubuntu: New Bug description: Description Umbrella task for SGX mainline kernel features. Target Kernel: 5.4 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827972] 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 1827972 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/1827972 Title: The noise keeps occurring when Headset is plugged in on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Plug in headset 2. Select Headset mode Expected result: There is no noise when headset is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
** Also affects: oem-priority Importance: Undecided Status: New -- 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/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827977] [NEW] eventinj in ubuntu_kvm_unit_tests failed on B-KVM
Public bug reported: FAIL eventinj (13 tests, 1 unexpected failures) # TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/eventinj.flat -smp 1 # -initrd /tmp/tmp.0h33pnhsnZ qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 Try to divide by 0 DE isr running divider is 0 Result is 150 PASS: DE exception Try int 3 BP isr running After int 3 PASS: BP exception Sending vec 33 to self irq1 running After vec 33 to self PASS: vec 33 Try int $33 irq1 running After int $33 PASS: int $33 Sending vec 32 and 33 to self irq1 running irq0 running After vec 32 and 33 to self PASS: vec 32/33 Sending vec 32 and int $33 irq1 running irq0 running After vec 32 and int $33 PASS: vec 32/int $33 Sending vec 33 and 62 and mask one with TPR irq1 running After 33/62 TPR test PASS: TPR irq0 running Before NP test NP isr running 400a3d err=18 irq1 running After int33 PASS: NP exception Sending NMI to self After NMI to self FAIL: NMI Before NMI IRET test Sending NMI to self NMI isr running stack 0x465000 Sending nested NMI to self After nested NMI to self Nested NMI isr running rip=4003e4 After iret After NMI to self PASS: NMI Try to divide by 0 PF running DE isr running divider is 0 Result is 150 PASS: DE PF exceptions Before NP test PF running NP isr running 400ccd err=18 irq1 running After int33 PASS: NP PF exceptions Try int 33 with shadowed stack irq1 running After int 33 with shadowed stack PASS: int 33 with shadowed stack SUMMARY: 13 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:26:45 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1827977 Title: eventinj in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: FAIL eventinj (13 tests, 1 unexpected failures) # TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/eventinj.flat -smp 1 # -initrd /tmp/tmp.0h33pnhsnZ qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 Try to divide by 0 DE isr running divider is 0 Result is 150 PASS: DE exception Try int 3 BP isr running After int 3 PASS: BP exception Sending vec 33 to self irq1 running After vec 33 to self PASS: vec 33 Try int $33 irq1 running After int $33 PASS: int $33 Sending vec 32 and 33 to self irq1 running irq0 running After vec 32 and 33 to self PASS: vec 32/33 Sending vec 32 and int $33 irq1 running irq0 running After vec 32 and int $33 PASS: vec 32/int $33 Sending vec 33 and 62 and mask one with TPR irq1 running After 33/62 TPR test PASS: TPR irq0 running Before NP test NP isr running 400a3d err=18 irq1 running After int33 PASS: NP exception Sending NMI to self After NMI to self FAIL: NMI Before NMI IRET test Sending NMI to self NMI isr running stack 0x465000 Sending nested NMI to self After nested NMI to self Nested NMI isr running rip=4003e4 After iret After NMI to self PASS: NMI Try to divide by 0 PF running DE isr running divider is 0 Result is 150 PASS: DE PF exceptions Before NP test PF running NP isr running 400ccd err=18 irq1 running After int33 PASS: NP PF exceptions Try int 33 with shadowed stack irq1 running After int 33 with shadowed stack PASS: int 33 with shadowed stack SUMMARY: 13 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6
[Kernel-packages] [Bug 1827978] [NEW] [SGX]Flexible Launch Control
Public bug reported: Implement open source launch enclave and bundle it with the Linux kernel so that the kernel can generate launch tokens for enclaves that the user requests to run. Flexible Launch Control consists of: Enclave singing tool for kbuild (DONE) Launch Enclave and its user space (DONE) Host program for the LE that reads SIGSTRUCT instances from stdin and outputs them to stdout (DONE) Kbuild changes to generate LE signing key (IN PROGRESS) Driver changes to launch lehost using user space helper framework (IN PROGRESS) Kernel changes to link lehost to vmlinux (IN PROGRESS) Relevant URLs: Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le Kernel tree: https://github.com/jsakkine-intel/linux-sgx Target Kernel: 5.2 Target Release: 19.10 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.10 ** Description changed: Implement open source launch enclave and bundle it with the Linux kernel so that the kernel can generate launch tokens for enclaves that the user requests to run. Flexible Launch Control consists of: Enclave singing tool for kbuild (DONE) Launch Enclave and its user space (DONE) Host program for the LE that reads SIGSTRUCT instances from stdin and outputs them to stdout (DONE) Kbuild changes to generate LE signing key (IN PROGRESS) Driver changes to launch lehost using user space helper framework (IN PROGRESS) Kernel changes to link lehost to vmlinux (IN PROGRESS) Relevant URLs: Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le Kernel tree: https://github.com/jsakkine-intel/linux-sgx + + Target Kernel: 5.2 + Target Release: 19.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827978 Title: [SGX]Flexible Launch Control Status in intel: New Status in linux package in Ubuntu: New Bug description: Implement open source launch enclave and bundle it with the Linux kernel so that the kernel can generate launch tokens for enclaves that the user requests to run. Flexible Launch Control consists of: Enclave singing tool for kbuild (DONE) Launch Enclave and its user space (DONE) Host program for the LE that reads SIGSTRUCT instances from stdin and outputs them to stdout (DONE) Kbuild changes to generate LE signing key (IN PROGRESS) Driver changes to launch lehost using user space helper framework (IN PROGRESS) Kernel changes to link lehost to vmlinux (IN PROGRESS) Relevant URLs: Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le Kernel tree: https://github.com/jsakkine-intel/linux-sgx Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1827978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827979] [NEW] pcid in ubuntu_kvm_unit_tests failed on B-KVM
Public bug reported: FAIL pcid (3 tests, 1 unexpected failures) # TESTNAME=pcid TIMEOUT=90s ACCEL= ./x86/run x86/pcid.flat -smp 1 -cpu qemu64,+pcid timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/pcid.flat -smp 1 -cpu qemu64,+pcid # -initrd /tmp/tmp.a4xQyF7juj qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic PASS: CPUID consistency PASS: Test on PCID when disabled FAIL: Test on INVPCID when disabled SUMMARY: 3 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:31:38 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1827979 Title: pcid in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: FAIL pcid (3 tests, 1 unexpected failures) # TESTNAME=pcid TIMEOUT=90s ACCEL= ./x86/run x86/pcid.flat -smp 1 -cpu qemu64,+pcid timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/pcid.flat -smp 1 -cpu qemu64,+pcid # -initrd /tmp/tmp.a4xQyF7juj qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic PASS: CPUID consistency PASS: Test on PCID when disabled FAIL: Test on INVPCID when disabled SUMMARY: 3 tests, 1 unexpected failures ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:31:38 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760755] Re: Intel FPGA Phase 1 driver upstream
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Description: The FPGA upstream driver Phase 1 includes the FPGA driver framework and minimum function support with basic function can work, end users can write apps, image can be flushed and programed. The driver includes below modules: PCIe driver core FME driver core with PR support AFU driver core with DMA + region mmap support - Target Release: 18.10 - Target Kernel: 4.17 + Target Release: 19.10 + Target Kernel: TBD ** Tags removed: intel-kernel-18.10 ** Tags added: intel-kernel-19.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/1760755 Title: Intel FPGA Phase 1 driver upstream Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description: The FPGA upstream driver Phase 1 includes the FPGA driver framework and minimum function support with basic function can work, end users can write apps, image can be flushed and programed. The driver includes below modules: PCIe driver core FME driver core with PR support AFU driver core with DMA + region mmap support Target Release: 19.10 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1760755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730885] [NEW] [Feature] SGX mainline enabling
You have been subscribed to a public bug: Description Umbrella task for SGX mainline kernel features. Target Kernel: 5.4 Target Release: 19.04 ** Affects: intel Importance: Medium Status: Triaged ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-19.04 kernel kernel-da-key -- [Feature] SGX mainline enabling https://bugs.launchpad.net/bugs/1730885 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685997] Re: [Feature] TPM: TPM 2.0 MEI Driver Update
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685997 Title: [Feature] TPM: TPM 2.0 MEI Driver Update Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Intel® QAT uses MEI to talk to intel® PTT (Platform Trust Technology – firmware TPM. Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1685997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801287] Re: [VROC] Update MD RAID drivers to the latest upstream version
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801287 Title: [VROC] Update MD RAID drivers to the latest upstream version Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Update MD RAID drivers to the latest upstream version Include md/bitmap, raid0, raid1, raid10 and raid456. This capability takes advantage of MD's long history and extends it to support the Intel Matrix metadata format (IMSM). MD provides a path to full Intel Matrix feature compatibility with minimal kernel changes. MD driver extensions are in active development. Final version will be included in Shaohua Li's GIT repository: https://git.kernel.org/cgit/linux/kernel/git/shli/md.git/ Target Release: 19.04 Target Kernel: 5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827972] [NEW] The noise keeps occurring when Headset is plugged in on a Dell machine
Public bug reported: Steps to reproduce: 1. Plug in headset 2. Select Headset mode Expected result: There is no noise when headset is plugged in ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1820788 originate-from-1820806 originate-from-1820808 originate-from-1824447 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1820806 somerville ** Tags added: originate-from-1820788 originate-from-1820808 originate- from-1824447 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827972 Title: The noise keeps occurring when Headset is plugged in on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Plug in headset 2. Select Headset mode Expected result: There is no noise when headset is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
** Description changed: - Before do S3, there is not any HDMI or DP monitor connected. - After resume from S3, 4 HDMI/DP audio output devices appear. - Those HDMI/DP audio output devices are unavailable. + [Impact] + In our OEM projects, we often meet this issues, there is no any monitor plugged, + but in the gnome-sound-setting, there are 4 hdmi/dp audio devices. + + + [Fix] + We check the eld_valid when reporting the hdmi/dp jack event + + [Test Case] + On the problematic machines, we do s3 test without plugging monitor, there + is no hdmi audio device in the sound-setting. + On the machines without this problem, we do s3 test, pluggin/unplugging + monitor test, the hdmi audio work well as before. + + [Regression Risk] + Low. We have done many tests on machines with or without this problem, + there is no regression so far. ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] In our OEM projects, we often meet this issues, there is no any monitor plugged, but in the gnome-sound-setting, there are 4 hdmi/dp audio devices. [Fix] We check the eld_valid when reporting the hdmi/dp jack event [Test Case] On the problematic machines, we do s3 test without plugging monitor, there is no hdmi audio device in the sound-setting. On the machines without this problem, we do s3 test, pluggin/unplugging monitor test, the hdmi audio work well as before. [Regression Risk] Low. We have done many tests on machines with or without this problem, there is no regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827912] 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 1827912 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/1827912 Title: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound Status in linux package in Ubuntu: Incomplete Bug description: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though. The screen being on, or connected made no difference though. No change based on keyboard or mouse. Fixes tried: https://wiki.ubuntu.com/Audio/PositionReporting ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.0.7-steamvr-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andruid1668 F pulseaudio /dev/snd/controlC0: andruid1668 F pulseaudio /dev/snd/pcmC0D0p: andruid1668 F...m pulseaudio /dev/snd/controlC1: andruid1668 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 12:38:45 2019 InstallationDate: Installed on 2019-02-16 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: May 06 12:22:43 Workstation-0 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1668 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="kernel") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [All Series, Realtek ALC1150, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-06T12:22:03.874818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826911] Re: hns: fix socket accounting
** 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/1826911 Title: hns: fix socket accounting Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] It is possible for a socket to use more memory than permitted on systems using the hns network driver. [Fix] b1ccd4c0ab6ef net: hns: fix skb->truesize underestimation [Test Case] Regression tested only. [Regression Risk] Trivial fix local to a single driver only used on ARM servers based on the Hi1616 SoC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
As per Seth's suggestion, I tried ratelimiting the cma_alloc messages:
diff --git a/mm/cma.c b/mm/cma.c
index c7b39dd3b4f6..56d2a046f689 100644
--- a/mm/cma.c
+++ b/mm/cma.c
@@ -477,7 +477,7 @@ struct page *cma_alloc(struct cma *cma, size_t count,
unsigned int align,
page_kasan_tag_reset(page + i);
}
- if (ret && !no_warn) {
+ if (ret && !no_warn && printk_ratelimit()) {
pr_err("%s: alloc failed, req-size: %zu pages, ret: %d\n",
__func__, count, ret);
cma_debug_show_areas(cma);
This drops the cma_alloc error message count down from 10758 to 21.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors at boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
On some arm64 systems[*] we are seeing a spew of messages on the
console:
[ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
[ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12
[ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12
This appears to be non-fatal - impacted systems all eventually boot.
But, at least in the case of the HP m400, it slows down boot enough
that MAAS' default timeout will expire before completing deployment.
[*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well
as an HP m400 (APM X-Gene) cartridge - although, not on another one
that - in theory - should be identical.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827967] 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 1827967 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/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Before do S3, there is not any HDMI or DP monitor connected. After resume from S3, 4 HDMI/DP audio output devices appear. Those HDMI/DP audio output devices are unavailable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827912] Re: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound
It sounds like this might be noise on the motherboard itself. Especially if you are hearing crackling when no sound is playing. I don't think there's much we can do about this in software, although the kernel guys sometimes have some tricks they can do to make sound chips less noisy... I personally recommend using a USB audio DAC or "USB sound card" to avoid such problems with motherboard noise. It is a very common hardware problem. You will also get higher quality sound from a USB DAC. I am also moving this bug to the kernel, just in case there's anything that can be done to reduce the problem there. ** Summary changed: - [All Series, Realtek ALC1150] Crackling sound + [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827912 Title: [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound Status in linux package in Ubuntu: New Bug description: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though. The screen being on, or connected made no difference though. No change based on keyboard or mouse. Fixes tried: https://wiki.ubuntu.com/Audio/PositionReporting ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.0.7-steamvr-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andruid1668 F pulseaudio /dev/snd/controlC0: andruid1668 F pulseaudio /dev/snd/pcmC0D0p: andruid1668 F...m pulseaudio /dev/snd/controlC1: andruid1668 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 12:38:45 2019 InstallationDate: Installed on 2019-02-16 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: May 06 12:22:43 Workstation-0 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1668 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="kernel") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [All Series, Realtek ALC1150, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-06T12:22:03.874818 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825777] Re: False positive test result in run_netsocktests from net in ubuntu_kernel_selftest
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) 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/1825777 Title: False positive test result in run_netsocktests from net in ubuntu_kernel_selftest Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: In Progress Bug description: == SRU Justification == The run_netsocktests from net in ubuntu_kernel_selftest will be marked as passed regardless the actual test result from the ./socket: selftests: net: run_netsocktests running socket test [FAIL] ok 1..6 selftests: net: run_netsocktests [PASS] This is because the test script itself has been successfully executed, and make it return 0. == Fix == 30c04d79 (selftests/net: correct the return value for run_netsocktests) This can be cherry-picked into all of our kernels. == Test == Patch tested and submitted to the upstream. == Regression Potential == Changes limit to the testing tool, and it's is expected to see failures from this test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827912] [NEW] [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound
You have been subscribed to a public bug: Issue: Audio Crackling Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though Testing: There is crackling coming from any speakers (headsets or brand-new speakers with no known issues). Crackling does not seem to be related to audio (it can occur even with sound turned off in the sound-control menu). (it does stop when power to speakers are removed) Video play back and during games seems to be when the issue is the worst. Scrolling on pages or hovering over UI objects also seems to trigger it too though. The screen being on, or connected made no difference though. No change based on keyboard or mouse. Fixes tried: https://wiki.ubuntu.com/Audio/PositionReporting ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.0.7-steamvr-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andruid1668 F pulseaudio /dev/snd/controlC0: andruid1668 F pulseaudio /dev/snd/pcmC0D0p: andruid1668 F...m pulseaudio /dev/snd/controlC1: andruid1668 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 12:38:45 2019 InstallationDate: Installed on 2019-02-16 (78 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: May 06 12:22:43 Workstation-0 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=1668 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="kernel") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [All Series, Realtek ALC1150, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-DELUXE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-06T12:22:03.874818 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- [ASUS Z87I-DELUXE, Realtek ALC1150] Crackling sound https://bugs.launchpad.net/bugs/1827912 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827967] [NEW] There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
Public bug reported: Before do S3, there is not any HDMI or DP monitor connected. After resume from S3, 4 HDMI/DP audio output devices appear. Those HDMI/DP audio output devices are unavailable. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1760814 originate-from-1819118 originate-from-1822747 somerville ** Tags added: originate-from-1822747 somerville ** Tags added: originate-from-1760814 originate-from-1819118 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Before do S3, there is not any HDMI or DP monitor connected. After resume from S3, 4 HDMI/DP audio output devices appear. Those HDMI/DP audio output devices are unavailable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782209] Re: KVM SnowRidge Split-lock disable
** Description changed: When bit 29 is set in Test Control MSR register 0x33, a #AC execption is generated for split locked accesses at all CPL irrespective of CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK assertion. Then developers can reconstruct their program accordingly Upstream target linux 5.2 - Target Release: 19.04 + Target Release: 19.10 ** Tags removed: intel-virt-19.04 ** Tags added: intel-virt-19.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/1782209 Title: KVM SnowRidge Split-lock disable Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: New Bug description: When bit 29 is set in Test Control MSR register 0x33, a #AC execption is generated for split locked accesses at all CPL irrespective of CR0.AM or EFLAGS.AC. This feature can help developers to capture memory accesses that across cachelines with #LOCK assertion. Then developers can reconstruct their program accordingly Upstream target linux 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782205] Re: KVM SnowRidge enable new ISAs
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782205 Title: KVM SnowRidge enable new ISAs Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in xen package in Ubuntu: Invalid Bug description: Add KVM support for SnowRidge New Instructions: GFNI and CLDEMOT GFNI: New instruction to compute an affine transformation in the Galois Field. The instruction is described here: https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf CLDEMOT: New instruction to hint to hardware that a cache line is likely to be shared. This is used to improve core-to-core communication. Upstream Target is Linux 4.20 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)
** Description changed: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 5.1/Qemu-3.10 - Target Release: 19.04 + Target Release: 19.10 ** Tags removed: intel-virt-19.04 ** Tags added: intel-virt-19.10 ** Description changed: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages - Upstream target linux 5.1/Qemu-3.10 + Upstream target linux 5.3/Qemu-3.10 Target Release: 19.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/1782206 Title: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Triaged Status in xen package in Ubuntu: Incomplete Bug description: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 5.3/Qemu-3.10 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823588] Re: [bug]kernel_physical_mapping_init regression in v4.20-rc1
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
** No longer affects: linux
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: intel
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Description changed:
Description:
A new warning introduced in v4.20-rc1 is triggered by the pmem use case for
memory hotplug:
WARNING: CPU: 3 PID: 998 at arch/x86/include/asm/tlbflush.h:460
__flush_tlb_all+0x1b/0x3a
The fix is to drop those __flush_tlb_all calls, but requests to
strengthen the safety of kernel_physical_mapping_init to give confidence
that it is safe to remove those calls is thus far leading to boot hangs.
Commits in next:(should be in 5.1, after merged, commit id will be changed)
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
0a9fe8ca844d x86/mm: Validate kernel_physical_mapping_init() PTE population
4369deaa2f02 generic/pgtable: Introduce set_pte_safe()
0cebbb60f759 generic/pgtable: Introduce {p4d,pgd} _same()
c683c37cd132 generic/pgtable: Make {pmd, pud} _same() unconditionally
available
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
- Targeted Release: 19.10
- Targeted Kernel: 5.1
+ Targeted Release: 19.04
+ Targeted Kernel: 5.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823588
Title:
[bug]kernel_physical_mapping_init regression in v4.20-rc1
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description:
A new warning introduced in v4.20-rc1 is triggered by the pmem use case for
memory hotplug:
WARNING: CPU: 3 PID: 998 at arch/x86/include/asm/tlbflush.h:460
__flush_tlb_all+0x1b/0x3a
The fix is to drop those __flush_tlb_all calls, but requests to
strengthen the safety of kernel_physical_mapping_init to give
confidence that it is safe to remove those calls is thus far leading
to boot hangs.
Commits in next:(should be in 5.1, after merged, commit id will be changed)
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
0a9fe8ca844d x86/mm: Validate kernel_physical_mapping_init() PTE population
4369deaa2f02 generic/pgtable: Introduce set_pte_safe()
0cebbb60f759 generic/pgtable: Introduce {p4d,pgd} _same()
c683c37cd132 generic/pgtable: Make {pmd, pud} _same() unconditionally
available
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
Targeted Release: 19.04
Targeted Kernel: 5.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1823588/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823588] Re: [bug]kernel_physical_mapping_init regression in v4.20-rc1
git tag --contains ba6f508d0ec4
v5.0
v5.0-rc1
v5.0-rc2
...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1823588
Title:
[bug]kernel_physical_mapping_init regression in v4.20-rc1
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description:
A new warning introduced in v4.20-rc1 is triggered by the pmem use case for
memory hotplug:
WARNING: CPU: 3 PID: 998 at arch/x86/include/asm/tlbflush.h:460
__flush_tlb_all+0x1b/0x3a
The fix is to drop those __flush_tlb_all calls, but requests to
strengthen the safety of kernel_physical_mapping_init to give
confidence that it is safe to remove those calls is thus far leading
to boot hangs.
Commits in next:(should be in 5.1, after merged, commit id will be changed)
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
0a9fe8ca844d x86/mm: Validate kernel_physical_mapping_init() PTE population
4369deaa2f02 generic/pgtable: Introduce set_pte_safe()
0cebbb60f759 generic/pgtable: Introduce {p4d,pgd} _same()
c683c37cd132 generic/pgtable: Make {pmd, pud} _same() unconditionally
available
ba6f508d0ec4 x86/mm: Drop usage of __flush_tlb_all() in
kernel_physical_mapping_init()
Targeted Release: 19.04
Targeted Kernel: 5.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1823588/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801668] Re: [AEP] ndctl test failed (21/24) and latest commits needed
** Changed in: intel Status: Fix Committed => Fix Released ** No longer affects: linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801668 Title: [AEP] ndctl test failed (21/24) and latest commits needed Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: Description: ndctl testing for AEP: make --no-print-directory check-TESTS FAIL: libndctl FAIL: dsm-fail PASS: dpa-alloc PASS: parent-uuid PASS: multi-pmem PASS: create.sh PASS: clear.sh PASS: pmem-errors.sh PASS: daxdev-errors.sh PASS: multi-dax.sh PASS: btt-check.sh PASS: label-compat.sh PASS: blk-exhaust.sh PASS: sector-mode.sh PASS: inject-error.sh PASS: btt-errors.sh PASS: hugetlb PASS: btt-pad-compat.sh PASS: firmware-update.sh PASS: ack-shutdown-count-set PASS: rescan-partitions.sh FAIL: inject-smart.sh PASS: monitor.sh PASS: max_available_extent_ns.sh make[5]: Nothing to be done for `all'. Testsuite summary for ndctl 62+ # TOTAL: 24 # PASS: 21 # SKIP: 0 # XFAIL: 0 # FAIL: 3 # XPASS: 0 # ERROR: 0 See test/test-suite.log Please report to linux-nvd...@lists.01.org make[4]: *** [test-suite.log] Error 1 make[3]: *** [check-TESTS] Error 2 make[2]: *** [check-am] Error 2 make[1]: *** [check-recursive] Error 1 make: *** [check] Error 2 Reproduce Steps: 1. Build and install kernel when doing ndctl testing, this need kernel ndctl test kernel module support. a.Download source kernel For exmaple: wget https://packages.ubuntu.com/cosmic/linux-source-4.18.0 or git clone git://kernel.ubuntu.com/ubuntu/ubuntu-cosmic.git b.Configure, build and install kernel # yes ''|make oldconfig # Ubuntu set CONFIG_LIBNVDIMM to ‘M’ make menuconfig -> Processor type and features -> Support non-standard NVDIMMs and ADR protected memory set to 'm' (Turn down two pages) # make –j`nproc` # make M=tools/testing/nvdimm # make M=tools/testing/nvdimm modules_install # make modules_install # make install 2. download ndctl source package download from github https://github.com/pmem/ndctl 3) Build ndctl test package # apt install –y autogen autoconf libopenr2-bin automake ranlib nvptx-tools libtool asciidoctor libkmod-dev libkmod2 libudev-dev uuid-dev libcjson-dev libjson-c-dev # rpmbuild –bp ndctl.spec # cd ./BUILD/ndctl-62 # export LC_ALL=C (for Ubuntu) # ./autogen.sh # ./ configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64 --with-systemd-unit-dir --enable-test # export KVER=4.20.0 # yum install jq # make check Commits related with failed test case: b4d4702f30e0 tools/testing/nvdimm: improve emulation of smart injection 39611e83a28c tools/testing/nvdimm: Make DSM failure code injection an override 099b07a25fff acpi, nfit: Prefer _DSM over _LSR for namespace label reads 08e6b3c6e3a0 libnvdimm: Introduce locked DIMM capacity support 41cd8b70c37a libnvdimm, btt: add support for blk integrity 5e096ef3b29e6113a7aa6a7dc4871987efa99bcb nfit_test: when clearing poison, also remove badrange entries 89360b87c3efa5d265a3b43dd8fc245c8f4356e3 libnvdimm, badrange: remove a WARN for list_empty 9fb1a1903345fea598f48277576a3589a972b72e nfit_test: add error injection DSMs aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a libnvdimm: move poison list functions to a new 'badrange' file Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801251] Re: [AEP]Fix badblocks population for 'raw' namespaces
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: intel
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801251
Title:
[AEP]Fix badblocks population for 'raw' namespaces
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description
The driver is only initializing bb_res in the devm_memremap_pages()
paths, but the raw namespace case is passing an uninitialized bb_res to
nvdimm_badblocks_populate().
Fixes: e8d513483300 ("memremap: change devm_memremap_pages interface...")
Cc:
Cc: Christoph Hellwig
Reported-by: Jacek Zloch
Reported-by: Krzysztof Rusocki
Reviewed-by: Vishal Verma
Signed-off-by: Dan Williams
Target Release: 19.04
Target Kernel: 4.20
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801251/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801253] Re: [AEP]copy_to_iter_mcsafe() send incorrect param to check_copy_size()
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801253 Title: [AEP]copy_to_iter_mcsafe() send incorrect param to check_copy_size() Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description copy_to_iter_mcsafe() is passing in the is_source parameter as "false" to check_copy_size(). This is different than what copy_to_iter() does. Also, the addr parameter passed to check_copy_size() is the source so therefore we should be passing in "true" instead. Commits: dfb06cba8c73 Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801256] Re: [AEP]nd_region region12: allocation underrun: 0x0 of 0x1980000000 bytes
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801256 Title: [AEP]nd_region region12: allocation underrun: 0x0 of 0x198000 bytes Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description This was seen by a customer when trying to create a namespace: [1124286.189585] nd_region region12: allocation underrun: 0x0 of 0x198000 bytes [1124286.189604] ---[ cut here ]--- [1124286.189611] WARNING: CPU: 59 PID: 145367 at drivers/nvdimm/namespace_devs.c:913 size_store+0x85e/0x870 [1124286.189612] Modules linked in: hfsplus hfs isofs binfmt_misc vtsspp(OE) sep4_1(OE) sepint4_1(OE) socperf2_0(OE) pax(OE) ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc vfat fat dax_pmem nd_pmem device_dax nd_btt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf ipmi_ssif iTCO_wdt iTCO_vendor_support ioatdma mei_me joydev i2c_i801 lpc_ich shpchp [1124286.189645] mei wmi dca ipmi_msghandler nfit acpi_power_meter acpi_pad xfs libcrc32c ast i2c_algo_bit drm_kms_helper ttm crc32c_intel nvme i40e drm nvme_core ptp pps_core [last unloaded: vtsspp] [1124286.189656] CPU: 59 PID: 145367 Comm: ndctl Tainted: G OE 4.14.18-300.fc27.x86_64 #1 [1124286.189657] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.01.00.0694.120620170818 12/06/2017 [1124286.189658] task: 98a64a088000 task.stack: a9840e52 [1124286.189660] RIP: 0010:size_store+0x85e/0x870 [1124286.189661] RSP: 0018:a9840e523d38 EFLAGS: 00010282 [1124286.189662] RAX: 0042 RBX: 9991b119a008 RCX: [1124286.189663] RDX: RSI: 98a67efd6a38 RDI: 98a67efd6a38 [1124286.189663] RBP: 9991b15a3fc0 R08: 0760 R09: 0004 [1124286.189664] R10: f171b9971c40 R11: 0001 R12: [1124286.189665] R13: 9991b515f000 R14: 9991b515f3d0 R15: a9840e523d9e [1124286.189666] FS: 7f402255c780() GS:98a67efc() knlGS: [1124286.189667] CS: 0010 DS: ES: CR0: 80050033 [1124286.189667] CR2: 563419868608 CR3: 002ef88ac001 CR4: 007606e0 [1124286.189668] DR0: DR1: DR2: [1124286.189669] DR3: DR6: fffe0ff0 DR7: 0400 [1124286.189669] PKRU: 5554 [1124286.189670] Call Trace: [1124286.189677] ? __kmalloc+0x199/0x210 [1124286.189680] kernfs_fop_write+0x10b/0x190 [1124286.189683] __vfs_write+0x36/0x180 [1124286.189687] ? selinux_file_permission+0x116/0x130 [1124286.189691] ? security_file_permission+0x3c/0xb0 [1124286.189692] vfs_write+0xad/0x1a0 [1124286.189694] SyS_write+0x52/0xc0 [1124286.189698] do_syscall_64+0x75/0x180 [1124286.189701] entry_SYSCALL_64_after_hwframe+0x21/0x86 [1124286.189703] RIP: 0033:0x7f40218517a4 [1124286.189703] RSP: 002b:7ffcc1c0e948 EFLAGS: 0246 ORIG_RAX: 0001 [1124286.189704] RAX: ffda RBX: 000e RCX: 7f40218517a4 [1124286.189705] RDX: 000e RSI: 7ffcc1c0e990 RDI: 0003 [1124286.189706] RBP: 7ffcc1c0e990 R08: 000a R09: [1124286.189706] R10: R11: 0246 R12: 0003 [1124286.189707] R13: R14: 7f402255c6b0 R15: 0002 [1124286.189708] Code: 48 85 ed 75 04 49 8b 6d 10 4c 89 ef e8 2c a7 fc ff 4c 8b 44 24 38 4c 89 e1 48 89 ea 48 89 c6 48 c7 c7 a8 7b 0f 95 e8 5d 74 b5 ff <0f> ff e9 bb fd ff ff e8 f6 9c af ff 66 0f 1f 44 00 00 0f 1f 44 [1124286.189729] --[ end trace 39a78a4960fc8601 ]-- Commits: 12e3129e29b4 1e687220ef2d Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801254] Re: [AEP]EDAC may report the wrong DIMM when patrol scrubber finds an error
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801254 Title: [AEP]EDAC may report the wrong DIMM when patrol scrubber finds an error Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description Facebook reported that on Broadwell systems EDAC sometimes reports the wrong DIMM for a memory error found by the patrol scrubber. The issue is rooted in h/w that only provides a 4KB page aligned address for the error in this case. This means that the EDAC driver will point at the DIMM matching offset 0x0 in the 4KB page, but because of interleaving across channels and ranks the actual DIMM involved may be different if the error is on some other cache line within the page. Fix: We can't actually get EDAC to point to the right DIMM because we don't know the offset within the page. But we should fix EDAC to say "I don't know" instead of pointing to the wrong DIMM. We can check the MCi_MISC register to know whether the address was cache-line aligned or page aligned. Bits 5:0 give the least significant bit that is valid. So a value of 6 is for cache line aligned (8 on Optane DC equipped systems that bundle 4 processor cache lines into a single Optane DC cache line). It will be 12 for patrol scrubber reported errors. Once we know we have a problem we should see how much information we can provide just from the "mce" structure passed the the EDAC driver. 1) We can get the socket from looking at m->extcup (the CMCI from the patrol scrubber will have been delivered to a logical CPU on the same socket) 2) The memory controller number. I think the m->bank will tell us this Need to check in the EDS for IvyBridge, Haswell and Broadwell. 3) The channel number. Low bits of MCi_STATUS.MCACOD should provide this. Facebook said that for many of their systems this should be enough for them (as a lot of systems only have one DIMM populated per channel). Note that Skylake is allegedly unaffected as the patrol scrubber should provide a cacheline aligned address. We should test and confirm Commits: 8489b17ce29d9a35a36c08bbea93cdce4c98a6ad Target Kernel: 4.20 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801248] Re: [AEP]Add micro-optimizations to dax page pinning
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801248 Title: [AEP]Add micro-optimizations to dax page pinning Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description We think we can save a few cpu cycles when pinning user pages mmap'ed from dax by avoiding the memtype_lock when looking up the memory type, and cache the dev_pagemap structure so we don't need to search the radix tree for it for every page. Commits: df06b37ffe5a442503b7095b77b0a970df515459 Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801249] Re: [AEP]softlockup running dax.sh against latest ext4 dev tree
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801249 Title: [AEP]softlockup running dax.sh against latest ext4 dev tree Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description Investigate the lockup report running dax.sh against ext4. [ 17.232155] pmem2: detected capacity change from 0 to 134232408064 [ 238.399253] EXT4-fs (pmem0): DAX enabled. Warning: EXPERIMENTAL, use at your own risk [ 238.404495] EXT4-fs (pmem0): mounted filesystem with ordered data mode. Opts: dax [ 238.460013] Injecting memory failure for pfn 0x208900 at process virtual address 0x7f38f190 [ 238.462987] Memory failure: 0x208900: Killing dax-pmd:12226 due to hardware memory corruption [ 238.465781] Memory failure: 0x208900: recovery action for dax page: Recovered [ 264.699441] watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [dax-pmd:12226] [..] [ 264.714244] hardirqs last enabled at (106241291): [] _raw_spin_unlock_irq+0x29/0x40 [ 264.717185] hardirqs last disabled at (106241292): [] trace_hardirqs_off_thunk+0x1a/0x1c [ 264.720163] softirqs last enabled at (106237250): [] __do_softirq+0x32e/0x428 [ 264.722974] softirqs last disabled at (106237243): [] irq_exit+0xf6/0x100 [ 264.725701] CPU: 6 PID: 12226 Comm: dax-pmd Tainted: G OE 4.19.0-rc3+ #2350 [ 264.728398] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014 [ 264.731851] RIP: 0010:lock_is_held_type+0x46/0x60 [..] [ 264.757670] Call Trace: [ 264.758745] find_get_entries+0x195/0x3c0 [ 264.760133] pagevec_lookup_entries+0x1a/0x30 [ 264.761597] dax_layout_busy_page+0x9c/0x280 [ 264.763038] ? __lock_acquire+0x12fa/0x1310 [ 264.764469] ext4_break_layouts+0x48/0x100 [ 264.765869] ? ext4_punch_hole+0x108/0x5a0 [ 264.767267] ext4_punch_hole+0x110/0x5a0 [ 264.768646] ext4_fallocate+0x189/0xa40 [ 264.76] ? rcu_read_lock_sched_held+0x6b/0x80 [ 264.771532] ? rcu_sync_lockdep_assert+0x2e/0x60 [ 264.773040] vfs_fallocate+0x13f/0x270 [ 264.774373] ksys_fallocate+0x3c/0x70 [ 264.775694] __x64_sys_fallocate+0x1a/0x20 [ 264.777094] do_syscall_64+0x60/0x210 [ 264.778417] entry_SYSCALL_64_after_hwframe+0x49/0xbe Commits: d7782145e1ad f52afc93cd01 Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801250] Re: [AEP] mprotect clobbers _PAGE_DEVMAP
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801250 Title: [AEP] mprotect clobbers _PAGE_DEVMAP Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description [PATCH] mm: Preserve _PAGE_DEVMAP across mprotect() calls Commits: 4628a64591e6 Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801246] Re: [AEP]WARN triggered by the device-dax unit test with 4.19-rc1
Fix added in 4.19-rc6:
commit 41c9b1be335b5afc3b5fb71c5d16f9d5939cd13f
Author: Dave Jiang
Date: Mon Sep 10 16:18:29 2018 -0700
device-dax: Add missing address_space_operations
With address_space_operations missing for device dax, namely the
.set_page_dirty, we hit a kernel warning when running destructive
ndctl unit test: make TESTS=device-dax check
WARNING: CPU: 3 PID: 7380 at fs/buffer.c:581 __set_page_dirty+0xb1/0xc0
Setting address_space_operations to noop_set_page_dirty and
noop_invalidatepage for device dax to prevent fallback to
__set_page_dirty_buffers() and block_invalidatepage() respectively.
Fixes: 2232c6382a ("device-dax: Enable page_mapping()")
Acked-by: Jeff Moyer
Reported-by: Vishal Verma
Signed-off-by: Dave Jiang
Signed-off-by: Dan Williams
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: intel
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801246
Title:
[AEP]WARN triggered by the device-dax unit test with 4.19-rc1
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description
[ +0.003470] WARNING: CPU: 3 PID: 7380 at fs/buffer.c:581
__set_page_dirty+0xb1/0xc0
[ +0.001177] Modules linked in: nd_pmem(O) dax_pmem(O) device_dax(O)
nd_btt(O) nd_e820(O) nfit(O) libnvdimm(O) nfit_test_iomap(O)
[ 0.001941] CPU: 3 PID: 7380 Comm: lt-device-dax Tainted: G O 4.19.0-rc1 #3
[ +0.001423] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org 04/01/2014
[ +0.002023] RIP: 0010:__set_page_dirty+0xb1/0xc0
[ +0.000789] Code: 80 00 5b 4c 89 e6 48 89 ef 5d 41 5c 41 5d 41 5e e9 a4 ac
82 00 48 8b 00 f6 c4 02 74 d7 48 89 df e8 54 bb f6 ff 48 89 c6 eb ce <0f> 0b eb
92 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 41 55
[ +0.003122] RSP: 0018:c90001bbba38 EFLAGS: 00010046
[ +0.000911] RAX: 007fff800815 RBX: ea0008108000 RCX: eb851eb851eb851f
[ +0.001212] RDX: RSI: 880310c51560 RDI: 0046
[ +0.001203] RBP: 880310c51548 R08: R09: 0001
[ +0.001220] R10: c90001bbb9a8 R11: b200 R12: 0246
[ +0.001202] R13: 880310c51540 R14: 0001 R15: 88016dd68040
[ +0.001205] FS: 7f418f6cf780() GS:880311a0()
knlGS:
[ +0.001363] CS: 0010 DS: ES: CR0: 80050033
[ +0.000975] CR2: 7f418f6ee000 CR3: 0001a1a36003 CR4: 001606e0
[ +0.001217] Call Trace:
[ +0.000435] __set_page_dirty_buffers+0xad/0x100
[ +0.000791] set_page_dirty_lock+0x41/0x60
[ +0.000709] dio_bio_complete+0x12c/0x160
[ +0.000693] ? do_blockdev_direct_IO+0x1c8b/0x2b60
[ +0.000825] do_blockdev_direct_IO+0x1d29/0x2b60
[ +0.000827] ? ext4_dio_get_block_unwritten_sync+0x50/0x50
[ +0.000944] ? ext4_direct_IO+0x15a/0x790
[ +0.000681] ext4_direct_IO+0x15a/0x790
[ +0.000672] ? touch_atime+0xc6/0xd0
[ +0.000621] generic_file_read_iter+0xbb/0xd40
[ +0.000762] ? up_write+0x1c/0x80
[ +0.000565] ? ext4_file_write_iter+0x20d/0x400
[ +0.000789] __vfs_read+0x112/0x190
[ +0.000619] vfs_read+0x9e/0x150
[ +0.000418] ksys_pread64+0x74/0x90
[ +0.000505] do_syscall_64+0x60/0x210
[ +0.000466] entry_SYSCALL_64_after_hwframe+0x49/0xbe
[ +0.000618] RIP: 0033:0x7f418e7a1f63
[ +0.000437] Code: f3 a9 f2 ff e8 4e 5b 02 00 66 2e 0f 1f 84 00 00 00 00 00
0f 1f 40 00 83 3d e9 d8 2d 00 00 75 13 49 89 ca b8 11 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 34 c3 48 83 ec 08 e8 6b 15 02 00 48 89 04 24
[ +0.002233] RSP: 002b:7ffc3fb777e8 EFLAGS: 0246 ORIG_RAX:
0011
[ +0.000916] RAX: ffda RBX: 7f418f6ea000 RCX: 7f418e7a1f63
[ +0.000879] RDX: 1000 RSI: 7f418f6ea000 RDI: 0005
[ +0.000896] RBP: R08: 001b R09:
[ +0.000884] R10: R11: 0246 R12: 0005
[ +0.000879] R13: R14: 0004 R15: 2000
[ +0.000889] irq event stamp: 136672
[ +0.000443] hardirqs last enabled at (136671): []
_raw_spin_unlock_irqrestore+0x32/0x60
[ +0.001185] hardirqs last disabled at (136672): []
_raw_spin_lock_irqsave+0x22/0x80
[ +0.001120] softirqs last enabled at (136542): []
__do_softirq+0x32e/0x428
[ +0.001028] softirqs last disabled at (136535): []
irq_exit+0xf6/0x100
[ +0.000995] --[ end trace 2dbcab5579c2e08f ]--
$ git bisect log
git bisect start
good: [021c91791a5e7e85c567452f1be3e4c2c6cb6063] Linux 4.18-rc3
git bisect good 021c91791a5e7e85c567452f1be3e4c2c6cb6063
bad: [c953cc987ab87d180e1d5de2f1c217abe33aac77] libnvdimm, pmem: Restore page
attributes when clearing errors
git
[Kernel-packages] [Bug 1801244] Re: [AEP]Need to issue quick ARS if ARS came from ACPI uc error notification and ARS is already running
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801244 Title: [AEP]Need to issue quick ARS if ARS came from ACPI uc error notification and ARS is already running Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description If the poison creation path is executed while ARS is running as a background task, the call to Start ARS DSM with Flag1=1 will fail with ARS already in progress error. Likewise the following Start ARS DSM would also fail. How does linux handle this? After ARS background thread has completed, does linux know that there could still be unreported errors and re-execute the quick ARS to catch any remaining errors? Commits: cc3d3458d46f Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801245] Re: [AE{]Prevent any ARS attempts when capabilities are clear
** No longer affects: linux
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: intel
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801245
Title:
[AE{]Prevent any ARS attempts when capabilities are clear
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description
The v4.17 ARS reworks broke the kernel's honoring of "no ARS capability"
responses from the BIOS. The kernel unconditionally schedules ARS for all PMEM
regions. Fix up the implementation to fail all ARS when no capability is
present.
Ideally the BIOS would just not publish the DSMs, for ARS, but we
should handle capabilities being present or not regardless.
Target Kernel: 4.20
Target Release: 19.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1801245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801235] Re: [AEP]2LM performance mitigation: non-self-conflicting numa nodes
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801235 Title: [AEP]2LM performance mitigation: non-self-conflicting numa nodes Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description Extend the numa_emulation driver to allow uniform split of physical numa nodes based on a given value. 3b6c62f363a1 cc9aec03e58f Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1801235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774385] Re: Add support for Secure Erase, overwrite and enable security
git tag --contains d6548ae4d16d v5.0 git tag --contains 76ef5e172527 v5.0 git tag --contains 9db67581b91d v5.0 git tag --contains f2989396553a v5.0 git tag --contains 37833fb7989a v5.0 git tag --contains 4c6926a23b76 v5.0 git tag --contains 03b65b22ada8 v5.0 git tag --contains d2a4ac73f56a v5.0 git tag --contains 64e77c8c047f v5.0 git tag --contains 7d988097c546 v5.0 git tag --contains 89fa9d8ea7bd v5.0 git tag --contains 3c13e2ac747a v5.0 git tag --contains 926f74802cb1 v5.0 git tag --contains ecaa4a97b390 v5.0 git tag --contains 1f4883f300da v5.0 git tag --contains 37379cfc661e v5.0 ** Changed in: intel Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774385 Title: Add support for Secure Erase, overwrite and enable security Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Add support for the new DSMs defined in the DSM spec v1.7.4, including Enable NVDIMM Security, Secure Erase NVDIMM, Overwrite NVDIMM and Query Overwrite NVDIMM Status. More info and specs can be found in the CCB: https://vthsd.fm.intel.com/hsd/purley_platform/default.aspx#ccb/default.aspx?ccb_id=136313 Target Kernel: 5.0 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1774385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774385] Re: Add support for Secure Erase, overwrite and enable security
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Description: Add support for the new DSMs defined in the DSM spec v1.7.4, including Enable NVDIMM Security, Secure Erase NVDIMM, Overwrite NVDIMM and Query Overwrite NVDIMM Status. More info and specs can be found in the CCB: https://vthsd.fm.intel.com/hsd/purley_platform/default.aspx#ccb/default.aspx?ccb_id=136313 - Target Kernel: 4.21 + Target Kernel: 5.0 Target Release: 19.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/1774385 Title: Add support for Secure Erase, overwrite and enable security Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Add support for the new DSMs defined in the DSM spec v1.7.4, including Enable NVDIMM Security, Secure Erase NVDIMM, Overwrite NVDIMM and Query Overwrite NVDIMM Status. More info and specs can be found in the CCB: https://vthsd.fm.intel.com/hsd/purley_platform/default.aspx#ccb/default.aspx?ccb_id=136313 Target Kernel: 5.0 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1774385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827961] 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/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774365] Re: ext4: Fix Filesystem-DAX DMA vs Unmap
** No longer affects: linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774365 Title: ext4: Fix Filesystem-DAX DMA vs Unmap Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Use the new dax_layout_busy_page() and page-idle events to implement block unmap versus dma protection in ext4. Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1774365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827961] [NEW] Lenovo dock MAC Address pass through doesn't work in Ubuntu
Public bug reported: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "debug.tar.bz2" https://bugs.launchpad.net/bugs/1827961/+attachment/5261970/+files/debug.tar.bz2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: New Bug description: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck
After upgrading to 19.04 disco, the system is still too unstable to be useful. The current kernel is 5.0.0-13-lowlatency (buildd@lcy01-amd64-020). I note the Intel driver has not changed after the upgrade from 18.10 cosmic, i.e. still iwlwifi-7265D-29.ucode, packaged within linux- firmware version 1.178. The details of the stack trace are different, but the outcome is the same (attached). The wifi connection is lost and kernel error messages spew out to the log. Stopping and restarting wifi makes no difference. The only "solution" is to shut down the system and reboot. Luckily I have a usb dongle that uses rtlwifi firmware, which works OK. ** Attachment added: "disco kernel log when intel driver hang is reported" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+attachment/5261968/+files/bacchus-iwlwifi-hang-log-disco-2019-04-27 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776443 Title: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck Status in linux package in Ubuntu: Confirmed Bug description: dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is down! Happens sometimes after a few minutes, never more than 30 minutes. Easy to capture journalctl when the network connection hangs. Intel fails on 2.4 GHz or 5 GHz, using several different AP's. The same system runs stable and perfect with a USB dongle Realtek RTL8188CUS, but I have to blacklist iwlwifi in /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network activity while simply scanning and not connected to an AP. I've had similar problems with this system under 17.10, but it has become more reproducible under 18.04. I've back-levelled the driver as far as possible, but they all hang the network. Because version 29 firmware is the latest in the bionic repository, and also on the intel support web site, I won't confuse matters by reporting earlier ubuntu kernels or iwlwifi versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
This occurrs on a target machine during maas install. Apport is not
collected in this case.
** 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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
Note that in current disco things have gotten worse - our single page allocations have blown up to 11753: $ cat cma.disco.dmesg | grep "cma: cma_alloc(cma" | sed -r 's/.*count ([0-9]+)\,.*/\1/' | sort -n | uniq -c 11753 1 3 2 3 4 234 8 32 16 2 24 4 32 256 33 39 64 2 128 2 1024 I bisected this down to a backport of the following commit: 3e394f9413ec RDMA/hns: Modify qp specification according to UM Reverting that gets us down to 3029 single page allocations, freeing up about 34M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
The culprit for the 256 33 page allocations (that causes the fragmentation mentioned in comment #8) is the hisi_sas_v3_hw driver: [ 21.220867] Call trace: [ 21.223301] dump_backtrace+0x0/0x1b0 [ 21.226948] show_stack+0x24/0x30 [ 21.230251] dump_stack+0x90/0xb4 [ 21.233554] cma_alloc+0x3f4/0x430 [ 21.236942] dma_alloc_from_contiguous+0x70/0x80 [ 21.241544] __dma_direct_alloc_pages+0x14c/0x228 [ 21.246234] dma_direct_alloc_pages+0x48/0xc0 [ 21.250576] dma_direct_alloc+0x50/0x80 [ 21.254397] dma_alloc_attrs+0x94/0x128 [ 21.258218] dmam_alloc_attrs+0x68/0xb8 [ 21.262043] hisi_sas_alloc+0x360/0x538 [hisi_sas_main] [ 21.267257] hisi_sas_shost_alloc_pci+0xfc/0x170 [hisi_sas_v3_hw] [ 21.273337] hisi_sas_v3_probe+0xd8/0x360 [hisi_sas_v3_hw] [ 21.278810] local_pci_probe+0x44/0xa8 [ 21.282544] work_for_cpu_fn+0x20/0x30 [ 21.286279] process_one_work+0x1f0/0x430 [ 21.290274] worker_thread+0x248/0x488 [ 21.294009] kthread+0x134/0x138 [ 21.297223] ret_from_fork+0x10/0x18 I wonder if it'd be possible to adjust this allocation somehow. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9
upgraded the firmware on dradis to P9DSU20190404_IBM_prod_sign.pnor and tested with bionic and disco and the issue does not reproduce. Marking this bug as fix-committed, and if you are able to reproduce this again please re-open this bug. ** Changed in: ubuntu-power-systems Status: Incomplete => Fix Committed ** 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/1827335 Title: Unable to put offline CPU back online on Bionic/B-hwe-edge P9 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: You will see these CPUs in offline state after boot. ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline 156-159 ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online 1 tee: /sys/devices/system/cpu/cpu156/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online 1 tee: /sys/devices/system/cpu/cpu157/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online 1 tee: /sys/devices/system/cpu/cpu158/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online 1 tee: /sys/devices/system/cpu/cpu159/online: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1 ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-14-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 2 06:46:36 2019 ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 18:55:27 UTC 2019 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 39 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 79) max: 2.945 GHz (cpu 81) avg: 2.903 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827343] Re: CPU hard lockup when turning CPU back online on Bionic P9
upgraded the firmware on dradis to P9DSU20190404_IBM_prod_sign.pnor and tested with bionic and disco and the issue does not reproduce. Marking this bug as fix-committed, and if you are able to reproduce this again please re-open this bug. ** Changed in: ubuntu-power-systems Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1827343 Title: CPU hard lockup when turning CPU back online on Bionic P9 Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Found on another Boston Power9 box "dradis". Steps to reproduce: 1. Check online CPUs $ cat /sys/devices/system/cpu/online 0-159 2. Do a CPU hotplug to take one off: $ echo 0 | sudo tee /sys/devices/system/cpu/cpu159/online 0 3. Check dmesg, you should see: [ 410.890106] IRQ 174: no longer affine to CPU159 4. Put that CPU back online and check dmesg again: $ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online System complains about CPU hard lockup: [ 410.890106] IRQ 174: no longer affine to CPU159 [ 421.168052] Watchdog CPU:128 Hard LOCKUP [ 421.168054] Modules linked in: joydev input_leds mac_hid idt_89hpesx ipmi_powernv opal_prd ipmi_devintf ibmpowernv ofpart at24 cmdlinepart uio_pdrv_genirq uio powernv_flash mtd ipmi_msghandler vmx_crypto sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas uas usb_storage ast hid_generic i2c_algo_bit ttm drm_kms_helper usbhid syscopyarea sysfillrect sysimgblt hid fb_sys_fops crct10dif_vpmsum crc32c_vpmsum drm i40e aacraid [ 421.168108] CPU: 128 PID: 778 Comm: watchdog/128 Not tainted 4.15.0-48-generic #51-Ubuntu [ 421.168109] NIP: c0d082e8 LR: c016c3b0 CTR: c0ac5d80 [ 421.168111] REGS: c0003f9ffd80 TRAP: 0900 Not tainted (4.15.0-48-generic) [ 421.168112] MSR: 90009033 CR: 24000484 XER: [ 421.168118] CFAR: c016c3ac SOFTE: 0 GPR00: c016c3b0 c000200e55743af0 c16eb400 c000200e614a8f20 GPR04: 088c c000200e614a4360 c000fd6879b8 0008 GPR08: 0054cd92 389fd980 8080 0005 GPR12: c0ac5d80 cfad8000 c013e648 c00ff90e9640 GPR16: GPR20: c000200e55852b80 200e602d GPR24: c000200e614a8580 c0d01ff0 c000200e614a6fb8 GPR28: c000200e614a8880 088c c000200e614a8580 c000200e614a8f20 [ 421.168142] NIP [c0d082e8] _raw_spin_lock+0x28/0xe0 [ 421.168146] LR [c016c3b0] update_curr_rt+0x1d0/0x3f0 [ 421.168147] Call Trace: [ 421.168150] [c000200e55743af0] [c171dd78] __per_cpu_offset+0x0/0x4000 (unreliable) [ 421.168154] [c000200e55743b20] [c016c2b0] update_curr_rt+0xd0/0x3f0 [ 421.168156] [c000200e55743bb0] [c016c7bc] dequeue_task_rt+0x3c/0xf0 [ 421.168159] [c000200e55743bf0] [c014e9b0] deactivate_task+0xb0/0x160 [ 421.168161] [c000200e55743c70] [c0d0187c] __schedule+0x3bc/0xaf0 [ 421.168164] [c000200e55743d40] [c0d01ff0] schedule+0x40/0xc0 [ 421.168167] [c000200e55743d60] [c0144bd4] smpboot_thread_fn+0x284/0x290 [ 421.168169] [c000200e55743dc0] [c013e7e8] kthread+0x1a8/0x1b0 [ 421.168172] [c000200e55743e30] [c000b658] ret_from_kernel_thread+0x5c/0x84 [ 421.168173] Instruction dump: [ 421.168175] 7c0803a6 4b98 3c4c009e 38423140 7c0802a6 6000 fbe1fff8 f821ffd1 [ 421.168179] 7c7f1b78 3940 994d028d 814d0008 <7d201829> 2c09 40c20010 7d40192d But the CPU is actually back online: $ cat /sys/devices/system/cpu/online 0-159 $ cat /sys/devices/system/cpu/cpu159/online 1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 2 08:06 seq crw-rw 1 root audio 116, 33 May 2 08:06 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
There is now a kernel patch for cifs that is supposed to fix the buffer overflow in strcat. Details see https://patchwork.kernel.org/patch/10931327/ An alternative workaround is to downgrade the connection to SMB2 (mount option vers=2.0) as the bug only affects SMB2.1 and SMB3 code. Regarding the second issue (BUG: unable to handle kernel NULL pointer dereference at 0038) it is likely that it is triggered by a racecondition aswell, which isn't yet fixed. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Fix Committed Bug description: Ubuntu 18.04.2 LTS Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem We've seen the following bug many times since we introduced new machines running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. Three different machines are affected, so it's rather not a hardware issue. | detected buffer overflow in strcat | [ cut here ] | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! | invalid opcode: [#1] SMP PTI | Modules linked in: [...] | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 | RIP: 0010:fortify_panic+0x13/0x22 | [...] | Call Trace: | smb21_set_oplock_level+0x147/0x1a0 [cifs] | smb3_set_oplock_level+0x22/0x90 [cifs] | smb2_set_fid+0x76/0xb0 [cifs] | cifs_new_fileinfo+0x259/0x390 [cifs] | ? smb2_get_lease_key+0x40/0x40 [cifs] | ? cifs_new_fileinfo+0x259/0x390 [cifs] | cifs_open+0x3db/0x8d0 [cifs] | [...] (Full dmesg output attached) After hitting this bug there are many cifs related dmesg entries, processes lock up and eventually the systems freezes. The share is mounted using: //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks Currently we're testing the cifs mount options "cache=none" as the bug seems to be oplock related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827944] [NEW] Kernel 5.1 is unsupported (and nvidia-418.56 error)
Public bug reported: Installing mainline v5.1 from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.1/ , I get this error: ERROR (dkms apport): kernel package linux- headers-5.1.0-050100-generic is not supported Also, building nvidia modules fail; I'm not sure it's related/critical. See attached file for both logs. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dkms-kernel51-and-nvidia418.log" https://bugs.launchpad.net/bugs/1827944/+attachment/5261952/+files/dkms-kernel51-and-nvidia418.log -- 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/1827944 Title: Kernel 5.1 is unsupported (and nvidia-418.56 error) Status in dkms package in Ubuntu: New Bug description: Installing mainline v5.1 from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.1/ , I get this error: ERROR (dkms apport): kernel package linux- headers-5.1.0-050100-generic is not supported Also, building nvidia modules fail; I'm not sure it's related/critical. See attached file for both logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Thanks Gabe! I agree with you, would be really nice to have a quirk for that. It would be more easy to analyze that possibility with a datasheet for this adapter, which unfortunately I don't have. I'm on vacation until next week, I'll try to discuss that in linux-usb when I'm back, and pursue a kernel quirk instead of firmware-only fix. @Bryan, thanks for checking with the vendor, let us know the outcome. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] Re: AMD Rome : Additional patches
Jeff, Yes this works with Disco and 5.0 kernel. My objective is to submit these patches to 18.04.1 LTS. There are 3 other patches as well.(Launchpad:1816669). I was going to submit the patches under 18.10(cosmic) to the kernel team and request for 18.04.1(bionic) inclusion. Would that be the right way to do it? --thanks --kim -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: AMD Rome : Additional patches Status in linux package in Ubuntu: Confirmed Bug description: The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827934] 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/1827934 Title: HDMI Port not detected Status in linux package in Ubuntu: Confirmed Bug description: The HDMI port doesn't appears in the list xrandr and not working with an external monitor connected Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rog3rb0t 1841 F pulseaudio /dev/snd/controlC1: rog3rb0t 1841 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 13:18:07 2019 InstallationDate: Installed on 2019-05-06 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-53 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c94dc0c5-52e1-44e1-aa97-82e4df33df3f ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnNitroAN515-53:pvrV1.22:rvnCFL:rnFreed_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-53 dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827934] [NEW] HDMI Port not detected
Public bug reported: The HDMI port doesn't appears in the list xrandr and not working with an external monitor connected Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rog3rb0t 1841 F pulseaudio /dev/snd/controlC1: rog3rb0t 1841 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 6 13:18:07 2019 InstallationDate: Installed on 2019-05-06 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-53 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c94dc0c5-52e1-44e1-aa97-82e4df33df3f ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.22 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.22 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnNitroAN515-53:pvrV1.22:rvnCFL:rnFreed_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-53 dmi.product.sku: dmi.product.version: V1.22 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco hdmi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827934 Title: HDMI Port not detected Status in linux package in Ubuntu: Confirmed Bug description: The HDMI port doesn't appears in the list xrandr and not working with an external monitor connected Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696
[Kernel-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
If someone else has those issues with a USB-C Dock (Thunderbolt 3) I got rid of the issue by using the latest mainline Kernel: 5.1.0-050100-generic #201905052130 SMP Mon May 6 01:32:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux and the following Kernel config settings (/etc/default/grub): GRUB_CMDLINE_LINUX_DEFAULT=" quiet splash intel_idle.max_cstate=4 i915.enable_psr=0 i915.enable_dc=0 i915.enable_fbc=0 i915.enable_dp_mst=0" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage
[Kernel-packages] [Bug 1579410] Re: Cannot suspend HP ProLiant SE316M1R2
In case anyone finds this bug report when googling for this error: the
problem is that the hpsa driver (which drives many HP RAID controllers)
just doesn't support suspend.
The code (even in Linux 5.0.13) reads:
```
static int hpsa_suspend(__attribute__((unused)) struct pci_dev *pdev,
__attribute__((unused)) pm_message_t state)
{
return -ENOSYS;
}
static int hpsa_resume(__attribute__((unused)) struct pci_dev *pdev)
{
return -ENOSYS;
}
static struct pci_driver hpsa_pci_driver = {
.name = HPSA,
.probe = hpsa_init_one,
.remove = hpsa_remove_one,
.id_table = hpsa_pci_device_id, /* id_table */
.shutdown = hpsa_shutdown,
.suspend = hpsa_suspend,
.resume = hpsa_resume,
};
```
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1579410
Title:
Cannot suspend HP ProLiant SE316M1R2
Status in linux package in Ubuntu:
Expired
Bug description:
pm-suspend does not work on HP ProLiant SE316M1R2 system.
I am not sure if hardware actually supports that though, but there is
kernel crash (see syslog.txt attached with Call Trace) which maybe is
the cause.
Monitor goes off for few seconds but after that system resumes and
works as before.
Also, some interesting lines:
May 7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend():
hpsa_suspend+0x0/0x10 [hpsa] returns -38
May 7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback():
pci_pm_freeze+0x0/0xe0 returns -38
May 7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0
failed to freeze async: error -38s2disks
These lines also appears when using s2disk.
s2ram gives:
KMS graphics driver is in use, skipping quirks.
s2ram_do: Invalid argument
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.21.22
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Sat May 7 20:55:52 2016
HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3
InstallationDate: Installed on 2015-10-12 (208 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
eth0 no wireless extensions.
eth1 no wireless extensions.
lono wireless extensions.
MachineType: HP ProLiant SE316M1R2
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic
root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-21-generic N/A
linux-backports-modules-4.4.0-21-generic N/A
linux-firmware1.157
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago)
dmi.bios.date: 07/02/2013
dmi.bios.vendor: HP
dmi.bios.version: R02
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant SE316M1R2
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579410/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg
Rui submitted a patch to change to dev_notice() https://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git/commit /?h=next=3c7110fab805766450c5d2eac1c994d4c8c230d3 But with default log level in Ubuntu, I think dev_notice will be dumped to dmesg. Is it correct? I submitted another patch to change to dev_dbg(). Let's see if it gets in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1824690 Title: proc_thermal flooding dmesg Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: [ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91] [ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91] [ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91] [ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91] [ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91] [ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91] [ 41.572682] random: crng init done [ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting Kernel 4.18.0-18-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1175 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-15 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N24_25GU Package: thermald 1.7.0-5ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= acpi_os_name=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/18/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25GU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25GU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795659] Re: kernel panic using CIFS share smb2_push_mandatory_locks
Hi, have some news in this one. I've emailed Microsoft CIFS maintainers, they
recommended the following patch as a potential fix:
b98749cac4a6 ("CIFS: keep FileInfo handle live during oplock break").
There's a PPA with a kernel built including this patch, for those
interested in testing:
https://launchpad.net/~dragan-s/+archive/ubuntu/lp1795659 .
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1795659
Title:
kernel panic using CIFS share smb2_push_mandatory_locks
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
Description:Ubuntu 16.04.5 LTS
Release:16.04
Kernel: 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Under load, getting a system crash when accessing files on an SMB3
share. dmesg from crash attached. I can upload the crash dump if
needed.
Share is mounted with the following options:
"ro,_netdev,username=*,password=*,domain=*,vers=3.02,sec=ntlmsspi,nounix,noserverino,nobrl,cache=none"
Dmesg points to the cifs module
[ 2192.662345] BUG: unable to handle kernel NULL pointer dereference at
0038
[ 2192.662407] IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport
Hi Chris, as per comment #21, the issue exists in kernel 4.18.0-14, and was fixed in 4.18.0-15. So, you need to update your kernel. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826032] Re: linux-fips: 4.4.0-1009.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1826036 - phase: Holding before Promote to Proposed - phase-changed: Monday, 06. May 2019 14:34 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 06. May 2019 17:34 UTC reason: - promote-to-proposed: Holding -- builds not complete in ppa + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826032 Title: linux-fips: 4.4.0-1009.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826036 phase: Ready for Promote to Proposed phase-changed: Monday, 06. May 2019 17:34 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827916] Re: Enable eBPF JIT in the linux-azure kernels
This request is for the 16.04 and 18.04 kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1827916 Title: Enable eBPF JIT in the linux-azure kernels Status in linux-azure package in Ubuntu: New Bug description: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1827916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827916] [NEW] Enable eBPF JIT in the linux-azure kernels
Public bug reported: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1827916 Title: Enable eBPF JIT in the linux-azure kernels Status in linux-azure package in Ubuntu: New Bug description: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1827916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
Jeff, The second patch improves the fix against the amount of memory in the system. We still need both patches. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826354] Re: linux-azure: 4.15.0-1044.48 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 06. May 2019 15:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): - arch=amd64:channel=latest/beta' - snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): - arch=amd64:channel=latest/edge' + snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): + arch=amd64:channel=latest/candidate:rev=55' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826354 Title: linux-azure: 4.15.0-1044.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1826352 (trusty/linux-azure) derivatives: bug 1826351 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1826358 phase: Testing phase-changed: Monday, 06. May 2019 15:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): arch=amd64:channel=latest/candidate:rev=55' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
Sorry, I missed responding. This were run in separate VMs, this is under our curtin vmtest integration testing. Yes, let me get the q35 trace; it doesn't happen as often. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip Status in linux package in Ubuntu: Confirmed Bug description: 1. disco 2. # apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.0.0.13.14 Candidate: 5.0.0.13.14 Version table: *** 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3. installation completes sucessfully 4. Running an installation of Disco creating filesystems and probing things will hang (stuck task) every so often. When it happens, the kernel throws an oops and bad rip value. [ 967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds. [ 967.811787] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.815500] mdadm D0 12213 12207 0x [ 967.815503] Call Trace: [ 967.815509] __schedule+0x2d0/0x840 [ 967.815511] ? __switch_to_asm+0x40/0x70 [ 967.815512] ? __switch_to_asm+0x34/0x70 [ 967.815514] schedule+0x2c/0x70 [ 967.815516] schedule_preempt_disabled+0xe/0x10 [ 967.815518] __mutex_lock.isra.10+0x2e4/0x4c0 [ 967.815522] ? exact_lock+0x11/0x20 [ 967.815524] __mutex_lock_slowpath+0x13/0x20 [ 967.815528] mutex_lock+0x2c/0x30 [ 967.815530] __blkdev_get+0x7b/0x550 [ 967.815532] ? bd_acquire+0xd0/0xd0 [ 967.815533] blkdev_get+0x10c/0x330 [ 967.815535] ? bd_acquire+0xd0/0xd0 [ 967.815537] blkdev_open+0x92/0x100 [ 967.815539] do_dentry_open+0x143/0x3a0 [ 967.815540] vfs_open+0x2d/0x30 [ 967.815542] path_openat+0x2d4/0x16d0 [ 967.815547] ? put_device+0x17/0x20 [ 967.815552] ? scsi_device_put+0x2b/0x30 [ 967.815553] do_filp_open+0x93/0x100 [ 967.81] ? strncpy_from_user+0x56/0x1b0 [ 967.815558] ? __alloc_fd+0x46/0x140 [ 967.815560] do_sys_open+0x177/0x280 [ 967.815561] ? _cond_resched+0x19/0x30 [ 967.815563] __x64_sys_openat+0x20/0x30 [ 967.815566] do_syscall_64+0x5a/0x110 [ 967.815567] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.815568] RIP: 0033:0x7faa36406cce [ 967.815572] Code: Bad RIP value. [ 967.815573] RSP: 002b:7ffedb663f80 EFLAGS: 0246 ORIG_RAX: 0101 [ 967.815574] RAX: ffda RBX: 4000 RCX: 7faa36406cce [ 967.815575] RDX: 4000 RSI: 564df70257b0 RDI: ff9c [ 967.815576] RBP: 564df70257b0 R08: 564df70257b0 R09: [ 967.815576] R10: R11: 0246 R12: 7ffedb664240 [ 967.815577] R13: R14: 0001 R15: 564df7023e00 [ 967.799227] INFO: task mkfs.btrfs:3767 blocked for more than 120 seconds. [ 967.803509] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.807192] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.810235] mkfs.btrfs D0 3767 1866 0x [ 967.810239] Call Trace: [ 967.810251] __schedule+0x2d0/0x840 [ 967.810254] ? __switch_to_asm+0x34/0x70 [ 967.810256] ? __switch_to_asm+0x40/0x70 [ 967.810258] schedule+0x2c/0x70 [ 967.810260] schedule_timeout+0x258/0x360 [ 967.810277] wait_for_completion+0xb7/0x140 [ 967.810281] ? wake_up_q+0x80/0x80 [ 967.810293] __floppy_read_block_0+0x138/0x190 [floppy] [ 967.810298] ? floppy_cmos_show+0x30/0x30 [floppy] [ 967.810302] floppy_revalidate+0xf8/0x230 [floppy] [ 967.810307] check_disk_change+0x62/0x70 [ 967.810309] floppy_open+0x2ae/0x380 [floppy] [ 967.810311] __blkdev_get+0xe5/0x550 [ 967.810313] ? bd_acquire+0xd0/0xd0 [ 967.810315] blkdev_get+0x10c/0x330 [ 967.810316] ? bd_acquire+0xd0/0xd0 [ 967.810318] blkdev_open+0x92/0x100 [ 967.810321] do_dentry_open+0x143/0x3a0 [ 967.810323] vfs_open+0x2d/0x30 [ 967.810326] path_openat+0x2d4/0x16d0 [ 967.810328] ? filename_lookup.part.60+0xe0/0x170 [ 967.810332] ? strncpy_from_user+0x56/0x1b0 [ 967.810333] do_filp_open+0x93/0x100 [ 967.810353] ? strncpy_from_user+0x56/0x1b0 [ 967.810358] ? __alloc_fd+0x46/0x140 [ 967.810360] do_sys_open+0x177/0x280 [ 967.810362] ? _cond_resched+0x19/0x30 [ 967.810364] __x64_sys_openat+0x20/0x30 [ 967.810368] do_syscall_64+0x5a/0x110 [ 967.810369] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 967.810372] RIP: 0033:0x7f46b99374db [ 967.810377] Code: Bad RIP value. [ 967.810378] RSP: 002b:7ffc9e849d70 EFLAGS: 0246 ORIG_RAX: 0101 [
[Kernel-packages] [Bug 1827880] Re: bionic/linux: completely remove snapdragon files from sources
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2019-May/100541.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/1827880 Title: bionic/linux: completely remove snapdragon files from sources Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] As requested by bug 1820868, we have split bionic/linux-snapdragon to its own source package and own git branch for better maintainability. Functionally that split was complete, however some leftover files where not removed from the sources leaving some dead files on the tree. [Fix] Sauce patch to remove all the files that were previously used to produce the snapdragon binaries from the linux master source. [Test Case] Compile test bionic/linux source and verify that nothing breaks. [Regression potential] Minimum. The fix is to remove files that are not being used anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
