[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver
** Changed in: intel Status: Triaged => 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/1730832 Title: [Feature] Add xHCI debug device support in the driver Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description xHCI compatible USB host controllers(i.e. super-speed USB3 controllers) can be implemented with the Debug Capability(DbC). It presents a debug device which is fully compliant with the USB framework and provides the equivalent of a very high performance full-duplex serial link. The debug capability operation model and registers interface are defined in 7.6.8 of the xHCI specification, revision 1.1. The DbC debug device shares a root port with the xHCI host. By default, the debug capability is disabled and the root port is assigned to xHCI. When the DbC is enabled, the root port will be assigned to the DbC debug device, and the xHCI sees nothing on this port. This implementation uses a sysfs node named under the xHCI device to manage the enabling and disabling of the debug capability. When the debug capability is enabled, it will present a debug device through the debug port. This debug device is fully compliant with the USB3 framework, and it can be enumerated by a debug host on the other end of the USB link. As soon as the debug device is configured, a TTY serial device named /dev/ttyDBC0 will be created. One use of this link is running a login service on the debug target. Hence it can be remote accessed by a debug host. Another use case can probably be found in servers. It provides a peer-to-peer USB link between two host-only machines. This provides a reasonable out-of-band communication method between two servers. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764792] [NEW] Build Nvidia drivers in conjunction with kernel
Public bug reported: We want to deliver a great out of the box experience of Ubuntu users running on Nvidia GPU enabled platforms (including instances in the cloud). Can we explore the possibility of pre-building the nvidia drivers alongside the kernel build, but not pre-link the drivers. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1764792 Title: Build Nvidia drivers in conjunction with kernel Status in linux package in Ubuntu: New Bug description: We want to deliver a great out of the box experience of Ubuntu users running on Nvidia GPU enabled platforms (including instances in the cloud). Can we explore the possibility of pre-building the nvidia drivers alongside the kernel build, but not pre-link the drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645521] Re: [Feature] ISH (Intel Sensor Hub) support
** 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/1645521 Title: [Feature] ISH (Intel Sensor Hub) support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Integrete ISH kernel driver and ISH driver should provoide following interface to user (1) Batch ModeGet the hardware batch buffer size/count,Set the batch timeout value (2) Wakeup/non-wakeupchecking if one sensor is wakeup instance or non-wakeup instance.For wakeup instance, when batch buffer is full or wait timeout, system must be woken up and receive batched sensor events. (3) Timestamp expose the sensor event timestamp to user space for sync (4) physical sensors-support exposing following physical sensors:Accelerometer,Gyroscope,Magnetic,Field,Pressure,Light,Proximity (5) Advanced sensorsupport exposing following advanced sensors: Gravity,Linear Acceleration,Rotation Vector,Orientation,Game Rotation,Geomagentic Rotation,Step Detector,Step Counter,Terminal,Significant motion,Wakeup Gesture,Glance Gesture,Tilt,PanZoon,Lift and Look (6)multiple sensor instance support (7)private command support support set/get path for private command set and response get, because some advanced sensor needs different special command to work properly. (8)User defined sensor support--- exposing non-pre-defined sensors. Because customer may add a new sensor in firmware, and hope sensor driver can expose it as a unknown sensor automatically, then application can use it directly without any code change. HW: Broxton-p Upstream Schedule: Basic Sensor Driver: 4.9 Advanced Sensor Driver: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689373] Re: disable NOUVEAU
** Description changed: Nouveau can be disabled in linux-aws, and must be disabled in order to disable some ACPI features. + + Colin King has demonstrated measurable boot speed improvements (up to 3%) + by disabling many ACPI features not used by cloud kernels. That work also + allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl). + Disk space utilization of the kernel is reduced: + /boot by ~200KB + /lib/modules by ~170 Kb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1689373 Title: disable NOUVEAU Status in linux-aws package in Ubuntu: In Progress Bug description: Nouveau can be disabled in linux-aws, and must be disabled in order to disable some ACPI features. Colin King has demonstrated measurable boot speed improvements (up to 3%) by disabling many ACPI features not used by cloud kernels. That work also allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl). Disk space utilization of the kernel is reduced: /boot by ~200KB /lib/modules by ~170 Kb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1689373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689374] Re: disable GPIOLIB, PINCTRL, and all consumers of them
** Description changed: These can be disabled in linux-aws, and must be disabled in order to disable various ACPI features. + + Colin King has demonstrated measurable boot speed improvements (up to 3%) + by disabling many ACPI features not used by cloud kernels. That work also + allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl). + Disk space utilization of the kernel is reduced: + /boot by ~200KB + /lib/modules by ~170 Kb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1689374 Title: disable GPIOLIB, PINCTRL, and all consumers of them Status in linux-aws package in Ubuntu: In Progress Bug description: These can be disabled in linux-aws, and must be disabled in order to disable various ACPI features. Colin King has demonstrated measurable boot speed improvements (up to 3%) by disabling many ACPI features not used by cloud kernels. That work also allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl). Disk space utilization of the kernel is reduced: /boot by ~200KB /lib/modules by ~170 Kb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1689374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689372] Re: disable many ACPI features
** Description changed: Many ACPI features can be disabled, per Colin King's research. + + Colin King has demonstrated measurable boot speed improvements (up to 3%) + by disabling many ACPI features not used by cloud kernels. That work also + allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl). + Disk space utilization of the kernel is reduced: + /boot by ~200KB + /lib/modules by ~170 Kb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1689372 Title: disable many ACPI features Status in linux-aws package in Ubuntu: In Progress Bug description: Many ACPI features can be disabled, per Colin King's research. Colin King has demonstrated measurable boot speed improvements (up to 3%) by disabling many ACPI features not used by cloud kernels. That work also allows us to unhook additional unused subsystems (Nouveau, gpiolib, pincntrl). Disk space utilization of the kernel is reduced: /boot by ~200KB /lib/modules by ~170 Kb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1689372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1676679] Re: datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD
Patch looks to have landed in the upstream kernel as of 4.11-rc4. This should be considered for SRU for Zesty (4.10) and Yakkety (4.8). I've marked it Fix Committed for Artful. $ git describe --contains 8f3dbfd79ed9ef9770305a7cc4e13dfd31ad2cd0 v4.11-rc4~28^2~49 $ git show 8f3dbfd79ed9ef9770305a7cc4e13dfd31ad2cd0 commit 8f3dbfd79ed9ef9770305a7cc4e13dfd31ad2cd0 Author: Kris Murphy Date: Thu Mar 16 10:51:28 2017 -0500 openvswitch: Add missing case OVS_TUNNEL_KEY_ATTR_PAD ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: openvswitch (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Yakkety) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** Changed in: linux (Ubuntu Zesty) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1676679 Title: datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Fix Committed Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Yakkety: Triaged Status in openvswitch source package in Yakkety: New Status in linux source package in Zesty: Triaged Status in openvswitch source package in Zesty: New Bug description: ---Problem Description--- Recreate and error info: Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from the Ubuntu 4.4 kernel. Iperf was used to send traffic between client VMs over VXLAN. The traffic did still flow, but every packet had to go to user space due to the flow creation failures, which drastically impacted performance and cpu utilization. When using VXLAN, the following error is showing up in dmesg openvswitch: netlink: Unknown IP tunnel attribute 14 Also there are tons of these errors in the openvswitch log 2017-03-01T15:50:47.860Z|00018|dpif(handler164)|WARN|system@ovs-system: failed to put[create] (Invalid argument) ufid:2d1a9aeb-7b24-4235-a208-a01f98237e60 recirc_id(0),dp_hash(0/0),skb_pri Debug showed that this attribute, OVS_TUNNEL_KEY_ATTR_PAD, was being seen in the switch statement in method, static int ip_tun_from_nlattr, in flow_netlink.c . Because there is no case for this attribute, the default is hit and returns an error. The issue was first seen using the packages in the Ubuntu 4.8 kernel, which is OVS 2.5. OVS 2.6 and 2.6.1 were also tried with the kernel packages and the same issue was seen. Tried building OVS 2.7 and loading the openvswitch-datapath-dkms_2.7.0-1_all.deb that got built but the issue persisted. The proposed patch seems to eliminate the error messages and also fixed the segmentation and performance issues that were seen. ---uname output--- stock 4.8 kernel Machine Type = p8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from the Ubuntu 4.4 kernel. Iperf was used to send traffic between client VMs over VXLAN. The traffic did still flow, but every packet had to go to user space due to the flow creation failures, which drastically impacted performance and cpu utilization. When using VXLAN, the following error is showing up in dmesg openvswitch: netlink: Unknown IP tunnel attribute 14 Link to the patch is https://patchwork.ozlabs.org/patch/738856/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1676679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683699] Re: [LTCTest][Opal][FW860] Oops: Kernel access of bad area, sig: 11 [#1] during frozen PE EEH error injection.
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683699 Title: [LTCTest][Opal][FW860] Oops: Kernel access of bad area, sig: 11 [#1] during frozen PE EEH error injection. Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Pridhiviraj Paidipeddi - 2016-08-13 08:28:54 == ---Problem Description--- Install P8 PowerNV 8284-22A Hardware with latest FW860 firmware having build SV860_028, and install a ubuntu 16.10 on top of it. During EEH FrozenPE error injection, observed a "Oops: Kernel access of bad area, sig: 11 [#1]" Contact Information = ppaid...@in.ibm.com ---uname output--- Linux lep8b 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:04:07 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---System Hang--- system is hung and need to do a Hard Power OFF/ON to bring the system up again. ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install a FW860 SV860_028 level of firmware on a P8 PowerNV 8284-22A Hardware. 2. Install a ubuntu 16.10 on top of it. 3. Inject below frozenPE EEH Error. echo 0:0:4:0:0 > /sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $? 4. Immediately we can observe a kernel Oops. *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. Call Traces: root@lep8b:~# echo 0:0:4:0:0 > /sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $? [ 271.110859] EEH: Frozen PE#0 on PHB#4 detected [ 271.110967] EEH: PE location: N/A, PHB location: N/A 0004:00:00.0 0604: 1014:03dc 0 root@lep8b:~# [ 277.108098] Unable to handle kernel paging request for data at address 0x0010 [ 277.108183] Faulting instruction address: 0xc0083c7c [ 277.108198] Oops: Kernel access of bad area, sig: 11 [#1] [ 277.108253] SMP NR_CPUS=2048 NUMA PowerNV [ 277.108310] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables leds_powernv ibmpowernv powernv_rng ipmi_powernv uio_pdrv_genirq ipmi_msghandler uio ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure be2net lpfc vxlan ip6_udp_tunnel udp_tunnel scsi_transport_fc ipr [ 277.109391] CPU: 9 PID: 973 Comm: eehd Not tainted 4.4.0-34-generic #53-Ubuntu [ 277.109467] task: c00feb3c2a20 ti: c00feb408000 task.ti: c00feb408000 [ 277.109542] NIP: c0083c7c LR: c0083c78 CTR: c0083c20 [ 277.109617] REGS: c00feb40b760 TRAP: 0300 Not tainted (4.4.0-34-generic) [ 277.109691] MSR: 90019033 CR: 28008822 XER: [ 277.109880] CFAR: c0008468 DAR: 0010 DSISR: 4000 SOFTE: 1 GPR00: c0083c78 c00feb40b9e0 c15b5d00 GPR04: 0001 c00feb40bac0 c02d74b54220 0f9f GPR08: 0026 GPR12: c0083c20 c7b45580 c00e63d8 c02d74c40100 GPR16: GPR20: c0d42468 GPR24: c0d42440 0100 c0036460 GPR28: c161a3f0 0001 c0281000 c000fe44 [ 277.110878] NIP [c0083c7c] pnv_eeh_reset+0x5c/0x170 [ 277.110931] LR [c0083c78] pnv_eeh_reset+0x58/0x170 [ 277.110981] Call Trace: [ 277.111009] [c00feb40b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 (unreliable) [ 277.111098] [c00feb40ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0 [ 277.75] [c00feb40bb00] [c0af472c] eeh_reset_device+0xd8/0x228 [ 277.111255] [c00feb40bba0] [c003c4c0] eeh_handle_normal_event+0x390/0x440 [ 277.111429] [c00feb40bc20] [c003c964] eeh_handle_event+0x184/0x370 [ 277.111601] [c00feb40bcd0] [c003cd28] eeh_event_handler+0x1d8/0x1e0 [ 277.111772] [c00feb40bd80] [c00e64e0] kthread+0x110/0x130 [ 277.111910] [c00feb40be30] [c0009538]
[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1682644 Title: IPR driver causes multipath to fail paths/stuck IO on Medium Errors Status in linux package in Ubuntu: Triaged Bug description: ---Problem Description--- IPR driver causes multipath to fail paths/stuck IO on Medium Errors This problem is resolved with this upstream accepted patch, scheduled for 4.11. The detailed problem description and resolution are described in the commit message. > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION > http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=785a470496d8e0a32e3d39f376984eb2c98ca5b3 Please apply to 17.04 and 16.04. The business justification for the SRU is: Clients with a dual-controller multipathed IPR configuration that eventually runs into failing disk/sectors, will experience an I/O hang once the drive reports a Medium Error, which can hang an application or even the root filesystem (whatever is doing I/O to the failing drive), potentially hanging the system. Thanks. ---Additional Hardware Info--- Dual (IPR) controller setup, multipath enabled ---Steps to Reproduce--- 1) Use a disk with bad sectors (or force such condition, via internal/special tools) 2) Multipath that disk 3) Run IO to the multipath device on the bad sectors 4) Both paths will be failed, and IO is stuck due to queue_if_no_path (enabled by default for IPR) The detailed problem description and resolution are described in the commit message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733864] Re: kernel 4.10.0-40 is hanging with a CPU soft lock
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733864 Title: kernel 4.10.0-40 is hanging with a CPU soft lock Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: Kernel 4.10.0-40-generic is causing CPU hung on POWER machines. I got this problem on a POWER8 KVM virtual machine [ 1912.003255] NMI watchdog: BUG: soft lockup - CPU#12 stuck for 24s! [dpkg-deb:31284] [ 1912.004496] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ipt_REJECT nf_reject_ipv4 xfrm_user xfrm_algo xt_addrtype xt_conntrack br_netfilter ebtable_filter ebtables ip6table_filter ip6_tables ib_srpt dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio tcm_qla2xxx qla2xxx vhost_scsi vhost usb_f_tcm tcm_usb_gadget libcomposite udc_core tcm_fc libfc scsi_transport_fc tcm_loop iscsi_target_mod target_core_file target_core_iblock target_core_pscsi target_core_mod ipmi_devintf ipmi_msghandler xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_tcpudp iptable_filter ip_tables x_tables openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) [ 1912.004575] znvpair(PO) spl(O) bridge 8021q garp mrp stp llc vmx_crypto kvm ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum virtio_blk [ 1912.004624] CPU: 12 PID: 31284 Comm: dpkg-deb Tainted: P O 4.10.0-40-generic #44~16.04.1-Ubuntu [ 1912.004626] task: c00775551e00 task.stack: c007755ac000 [ 1912.004627] NIP: 3fff86b71960 LR: 3fff86b7319c CTR: 002d [ 1912.004628] REGS: c007755afea0 TRAP: 0901 Tainted: P O (4.10.0-40-generic) [ 1912.004629] MSR: 8280f033 [ 1912.004635] CR: 42004442 XER: 2000 [ 1912.004636] CFAR: 3fff86b719b4 SOFTE: 1 GPR00: 00a4 3fffd53f7d70 3fff86ba5008 0040 GPR04: 038a20fc 3fff86467d4b 036c0ed8 002a GPR08: 3fff81c41010 000a20f5 0081 ffec0ed1 GPR12: 00a6 3fff86c8db30 [ 1912.004646] NIP [3fff86b71960] 0x3fff86b71960 [ 1912.004647] LR [3fff86b7319c] 0x3fff86b7319c [ 1912.004647] Call Trace: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736827] Re: Toshiba BIOS wrecked
** 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/1736827 Title: Toshiba BIOS wrecked Status in linux package in Ubuntu: Confirmed Bug description: I installed UBUNTU 17.10 - Dual Boot Windows 10, with GRUB2 as Bootloader on my expensive Toshiba Laptop - s50t-b (model #). Now Bios is basically useless, no change boot order, no load defaults, no system clock. what do I do? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755627] Re: ibrs/ibpb fixes result in excessive kernel logging
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Trusty:
Triaged
Status in linux source package in Xenial:
Triaged
Bug description:
Since at least kernel 4.4.0-116, every invocation of `sysctl -a`
results in kernel logs similar to the following:
% sysctl -a &>/dev/null; dmesg -T | tail -8
[Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0
[Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0
The output varies with the number of CPUs.
After digging a bit, it turns out this is triggered upon every read of
`kernel.ibrs_dump`:
% for i in {1..3}; do sysctl kernel.ibrs_dump; dmesg -T | tail -8; echo;
sleep 1; done
kernel.ibrs_dump = 0
[Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0
[Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0
kernel.ibrs_dump = 0
[Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0
[Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0
kernel.ibrs_dump = 0
[Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0
[Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4
[Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0
[Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0
Those tests were against an EC2 instance running Ubuntu 4.4.0-116.140-generic
4.4.98 per /proc/version_signature
Normally this would not be the biggest concern but we have tooling
that gathers instance info on a schedule, including sysctl output,
thus resulting in the kernel ring buffer being full of nothing but
said output in most cases and hindering live troubleshooting as a
result.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755627/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730770] Re: [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730770 Title: [Feature][CFL] Enable pmc_core driver for H, S, and U SKUs Status in intel: Incomplete Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Need to enable pmc_core driver for Coffee Lake so we can get at the slp_s0# counter, which measures S0ix residency. Target Kernel:4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737873] Re: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization)
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737873 Title: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization) Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: L2 CDP separates code and data in L2 cache allocation. First implemented in Gemini Lake processor. It's an extension of L2 CAT and similar to already released L3 CDP. The L2 CDP is supposed to be published in Dec SDM. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1737873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460900] Re: [Feature]Code/Data Prioritization (CDP) Enablment
Hi Xiong, Can we mark this 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/1460900 Title: [Feature]Code/Data Prioritization (CDP) Enablment Status in intel: Incomplete Status in linux package in Ubuntu: Fix Committed Status in xen package in Ubuntu: Fix Released Bug description: Code Data prioritization (CDP) is projected to be released before the MBE(memory b/w enforcement) as part of bdx This would be an extension of the CAT feature and the h/w would provide cache allocation for code and data seperately once the feature is enabled. This is added from customer requests who have very large code footprints and need to seperately prioritize data and code. Schedule: upstream: 4.10 kernel xen: 4.7 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1460900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591808] Re: [Feature] SKX: Intel® Cache Allocation Technology(CAT)
** Changed in: intel Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Expired => 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/1591808 Title: [Feature] SKX: Intel® Cache Allocation Technology(CAT) Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This item tracks Skylake-specifc work that needs to be performed on top of BDX CAT. HW: Purley Upstream schedule: v4.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645540] Re: [Feature] Crystal Ridge 2LM error reporting
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Invalid ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) 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/1645540 Title: [Feature] Crystal Ridge 2LM error reporting Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Bug description: In 2LM configurations we need to error reports to differentiate between errors in the "near" memory (DRAM used as cache) and "far" memory (Crystal ridge memory) HW: Apache Pass Upstream schedule: kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1676741] Re: [Bug] Surprise Link down causes the slot to go to a non-stop off/on
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) 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/1676741 Title: [Bug] Surprise Link down causes the slot to go to a non-stop off/on Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: A surprise link down may retrain very quickly, causing the same slot to generate a link up event before handling the link down completes. Since the link is active, the power off work queued from the first link down will cause a second down event when the power is disabled. The second down event should be ignored because the slot is already powering off; however, the "link up" event sets the slot state to POWERON before the event to handle this is enqueued, making the second down event believe it needs to do something. This creates a constant link up and down event cycle. Fix for this issue is still not merged upstream, and they are looking for a more complex fix. Its still in works. COMMIT ID TO BE UPDATED. Target Release: 18.04 Target Kernel: 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1676741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645966] Re: [Feature] GLK Enable UMIP - User Mode Instruction Prevention
Marking this Fix Released for Bionic which has a 4.15 based kernel now. ** Information type changed from Private to Public ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu Artful) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1645966 Title: [Feature] GLK Enable UMIP - User Mode Instruction Prevention Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Won't Fix Bug description: Executing user mode privileged instructions such as SMSW has been in the x86 processor since 80386 days. These instruction used by DOSEMU and other Software to emulate x86 instructions. Some comments from HPA below. UMIP enabling is trivial (a CR4 bit), except that a handful of applications (dosemu in particular) might depend on those instructions, especially SMSW. As we don't want to make it too easy for an application to disable UMIP while running, I'm wondering if we can use H.J.'s proposed flags scheme to mark that an executable needs to disable UMIP. On the other hand, if dosemu is the only app then it might be easier and better to emulate in a trap handler HW: Gemini Lake Uptream schedule: kernel:4.14 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685729] Re: [Feature]CNL:New device IDs for CNL
** 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/1685729 Title: [Feature]CNL:New device IDs for CNL Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: This task is to identify what new device IDs are required for CNL, whether they are published or not. Once that is clarified, documentations and device drivers need to update accordingly, and we will create sub-tasks for each device driver ID update. IDs to be added: Placeholder for CNL IDs that should be published. Device ID ## Kernel Version ## Commit ## Approved to be published == USB device/xDCI CNL-LP: 0x9dee CNL-H: 0xa36e ## v4.12 ## 682179592e ## Yes SMBus CNL-LP: 0x9da3 CNL-H: 0xa323 ## v4.13 ## 09a1de04d598 ## Yes I2C CNL-LP: 0x9dc5 0x9dc6 0x9de8 0x9de9 0x9dea 0x9deb CNL-H: 0xa368 0xa369 0xa36a 0xa36b ## v4.13 ## b418bbff36dd ## Yes HS-UART CNL-LP: 0x9da8 0x9da9 0x9dc7 CNL-H: 0xa328 0xa329 0xa347 ## v4.13 ## b418bbff36dd ## Yes SPI CNL-LP: 0x9daa 0x9dab 0x9dfb CNL-H: 0xa32a 0xa32b 0xa37b ## v4.13 ## b418bbff36dd fc0b2acc754a ## Yes GPIO CNL-LP: INT34BB CNL-H: INT3450 ## v4.14 ## 19a8a7771770 a663ccf0fea1 ## Yes SD Card CNL-LP: 0x9d5f CNL-H: 0xa375 ## v4.13 ## bc55dcd822f9 ## Yes eMMC CNL-LP: 0x9dc4 ## v4.13 ## bc55dcd822f9 ## Yes UFS CNL-LP: 0x9dfa CNL-H: N/A ## v4.13 ## 2c87ea97ce6a53fc8c98a796b34fed5b84aeff6b ## Yes NPK CNL-LP: 0x9da6 CNL-H: 0xa326 ## v4.14 ## efb3669e14 84331e1390 ## Yes Target Release: 17.10 Target Kernel : 4.14 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1685729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685723] Re: [Feature] GLK/CNL:eMMC 5.1 support
The following landed in 4.16-rc1 and would need to be considered for backporting. Adding a linux task for Bionic. 10f21df4a23540b5da8e88d1030ff8c37818e04f mmc: block: blk-mq: Add support for direct completion 88a516461ee07a994c0e7016faf85f3466de1d09 mmc: block: blk-mq: Separate card polling from recovery c89b4851c67fb7354862850ae181de883269487d mmc: block: Make card_busy_detect() accumulate all response error bits f47a1fe346b1568df0e9b158574b2939432313df mmc: block: blk-mq: Check error bits and save the exception bit when polling card busy 7701885e56cee3de4447c0653f9059b62844983b mmc: block: Check the timeout correctly in card_busy_detect() 0987c6b046e199b9b922a585c62e9503486fe0bc mmc: block: Check for transfer state in card_busy_detect() 92c0a0cc9483c6b9cc1b61273d30a0a601cb5e15 mmc: block: Add timeout_clks when calculating timeout 6b7a363d2ce83e3940dc0c3628e478fe95f23985 mmc: block: Reduce polling timeout from 10 minutes to 10 seconds 7eb43d537166c7d767af450901acd0ecbf94625c mmc: block: blk-mq: Stop using legacy recovery 42f532da3a44843668dbacc1838a028b0a9b7373 mmc: mmc_test: Do not use mmc_start_areq() anymore d2383318c5a626312d166217e3788e54b1650c56 mmc: core: Ensure cmd_completion is initialized 23a185254ace8e63dc4ca36e0315aed9440ae749 mmc: mmc_test: Ensure command queue is disabled for testing 1bec43a3b181baebdf8a4cd739b480a9132601d7 mmc: core: Remove option not to use blk-mq 0fbfd12518303e9b32ac9fd231439459eac848f9 mmc: block: Remove code no longer needed after the switch to blk-mq 126b62700386da782f83579e9b0431ea76c2da3d mmc: core: Remove code no longer needed after the switch to blk-mq 0562315b86372d2cdd9cc8924b92cfab37049fbc mmc: cqhci: Ensure macro parameters are wrapped in parentheses ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685723 Title: [Feature] GLK/CNL:eMMC 5.1 support Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: CNL will have eMMC5.1 capable host controller that includes new features: 1) Command queue support – making the data transfers highly efficient by offloading the software overhead into the controller. 2) eMMC 5.1 further improves the reliability of operation by utilizing an “enhanced strobe” at the PHY layer. The eMMC5.1 is backward compatible with the existing eMMC 4.51 and eMMC 5.0 Devices. Target Kernel:4.16 Target Release: 18.04 Target Platform: GLK/CNL To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1685723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704261] Re: [Feature] Crystal Ridge - synchronous fault support for ext4
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) 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/1704261 Title: [Feature] Crystal Ridge - synchronous fault support for ext4 Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Arrange for ext4 faults to resolve any required metadata updates before the fault returns to userspace. We either need this mechanism or the immutable file approach (LP#1704259). Target Kernel:4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702389] Re: [Feature] WIFI-CNL: Integrated Connectivity enablement for Cannon Lake
Marking the linux task Fix Released. I have left the linux-firmware task open so we can confirm we have this included there. Thanks. ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu Artful) Status: New => Won't Fix ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Information type changed from Private to Public ** Tags added: kernel -- 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/1702389 Title: [Feature] WIFI-CNL: Integrated Connectivity enablement for Cannon Lake Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Triaged Status in linux source package in Artful: Fix Released Status in linux-firmware source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Triaged Bug description: Description: Tracks the enablement of the integrated WiFi component in Cannon Lake. The WiFi component is called Pulsar. 9260 will be supported starting from 4.13. The first firmware that will be available publicly for 9260 is -33.ucode and this firmware will be supported by 4.13. Thunder Peak (ThP) comes with Jefferson Peak (JfP) as a radio component. It is supported in 4.11. The only missing part upstream is the firmware. Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1702389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713619] Re: [Feature] RDT: Disable most RDT features on Skylake server
** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713619 Title: [Feature] RDT: Disable most RDT features on Skylake server Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: There are serious errata in CMT, MBM and CAT sub-features of resource director technology. Disable these features by default on Skylake but provide a boot time argument to re-enable them for users who understand the errata and can use them for specific workloads. Commit IDs:(4.14) 0576113a387e0c8a5d9e24b4cd62605d1c9c0db8 1d9807fc64c131a83a96917f2b2da1c9b00cf127 d56593eb5eda8f593db92927059697bbf89bc4b3 Target Release : 17.10 Target Kernel: 4.14 (Need backporting into 17.10 from 4.14 to 4.13) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1713619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704711] Re: [Feature] CNL-Titan Ridge: USB 3.1 SuperSpeedPlus (SSP) support
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1704711 Title: [Feature] CNL-Titan Ridge: USB 3.1 SuperSpeedPlus (SSP) support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description In CNL there will be AIC called Titan Ridge that provides USB3.1 host and device side functionality. HW: Cannon Lake Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712031] Re: [Feature] PXE boot with Intel Omni-Path
** 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1712031 Title: [Feature] PXE boot with Intel Omni-Path Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Bug description: Description: This is about ability to PXE boot over Intel Fabric. Netboot initrd is missing infiniband kernel stack along with hfi1.ko (for 1st generation of Intel Omni-Path cards). In addition some firmware files required to load modules are also missing in initrd. This firmware came from existing linux-firmware package, but is not included in netboot initrd image. Add Intel Omni-Path Architecture (OPA) Firmware to initrd.gz The initrd.gz supplied on Ubuntu 17.04 is missing the following firmware listed below in the /lib/firmware directory. As a result, PXE boot over fabric fails. hfi1_dc8051.fw hfi1_fabric.fw hfi1_pcie.fw hfi1_sbus.fw Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1712031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704698] Re: [Feature] Northpeak Enabling
I assume this is now resolved for our 4.15 kernel in 18.04? Intel, please confirm. ** Changed in: intel 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/1704698 Title: [Feature] Northpeak Enabling Status in intel: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: Description Description: The NPK(North Peak) solution is composed of four major components.Hardware to connect the debug target to the host. DAL (DFX Abstraction Layer) to manage the target to host connection. NPKSDK connects to DAL and processes trace data using a decoder network. GUI and command line tools provide access to NPKSDK to configure and start / stop tracing. In CNL we have also Core side tracing that is new enabling. Stakeholders : To be filled out by Engineering Status : Base Enabling HW: Cannon Lake Target Kernel: v4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730569] Re: [Feature] Add JSON perf event lists for GLP(Goldmont Plus)
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Tags added: kernel ** Also affects: linux (Ubuntu Bionic) 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/1730569 Title: [Feature] Add JSON perf event lists for GLP(Goldmont Plus) Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Submit perf json event lists for Goldmont Plus once they are public in the SDM. Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730260] Re: [Feautre] RDT:Add better diagnostics to /sys/fs/resctrl RDT interface
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730260 Title: [Feautre] RDT:Add better diagnostics to /sys/fs/resctrl RDT interface Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Figuring out what went wrong is hard when the only error message you get is: bash: echo: write error: Invalid argument Add code to the kernel to implement a new file /sys/fs/resctrl/info/last_cmd_status that provides a more helpful message when a command fails. Commit Id list: 165d3ad884df4b30c3564a478b457b499345886f 29e74f35b2fed0ca3e8b31db157e1d183e9d0819 94457b36e8a5026443707b48dcf54b204e098fd7 9b3a7fd0f5fb583a8fdda678e8a87dff1717f7f3 c377dcfbee808efdb66cf1bb6b9f06fa26b2ad0a cfd0f34e4cd5f1a5ad7000a3104c37886a70bca9 Will be merged into 4.15-rc1 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728762] Re: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D
** Changed in: intel Status: Incomplete => Fix Released -- 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/1728762 Title: Update iwlwifi firmware for 3160, 3168, 7260, 7265 and 7265D Status in intel: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Trusty: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux-firmware source package in Zesty: Fix Released Status in linux-firmware source package in Artful: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: SRU Justification Impact: Intel wireless firmware WoWLAN functionality is vulnerable to some CVEs from the KRACK attack vulnerabilities, CVE-2017-13080 and CVE-2017-13081. Fix: Updated firmware from Intel containing fixes for these vulnerabilities. Test Case: Difficult to test; we are reliant on testing done by Intel. Regression Potential: There is always some possibility for regressions with firmware updates, but as these are bug fix updates the regression potential is minimal. I have been using the 7260 firmware for over a week now without issue. --- There are two parts of WIFI firmware update. Please double check if Ubuntu release has include them. A new firmware version for 8260 and 8265 WiFi devices. This our Core31 release (-34.ucode). https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=348d2b53326bcef4c260037cc7a6006fc80ca5bb A new firmware version for 3160, 3168, 7260, 7265 and 7265D Note: This firmware version hasn't been pulled into mainline yet. This includes a security fix. The patch in iwlwifi/linux-firmware.git is here: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=11e310f97470f91e26e6f3408b09871fd6cd3c5c To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1728762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730260] Re: [Feautre] RDT:Add better diagnostics to /sys/fs/resctrl RDT interface
165d3ad884df4b30c3564a478b457b499345886f x86/intel_rdt: Add documentation for "info/last_cmd_status" v4.15-rc1~148^2~6 29e74f35b2fed0ca3e8b31db157e1d183e9d0819 x86/intel_rdt: Add diagnostics when writing the tasks file v4.15-rc1~148^2~9 94457b36e8a5026443707b48dcf54b204e098fd7 x86/intel_rdt: Add diagnostics when writing the cpus file v4.15-rc1~148^2~8 9b3a7fd0f5fb583a8fdda678e8a87dff1717f7f3 x86/intel_rdt: Add framework for better RDT UI diagnostics v4.15-rc1~148^2~11 c377dcfbee808efdb66cf1bb6b9f06fa26b2ad0a x86/intel_rdt: Add diagnostics when writing the schemata file v4.15-rc1~148^2~10 cfd0f34e4cd5f1a5ad7000a3104c37886a70bca9 x86/intel_rdt: Add diagnostics when making directories v4.15-rc1~148^2~7 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730260 Title: [Feautre] RDT:Add better diagnostics to /sys/fs/resctrl RDT interface Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Figuring out what went wrong is hard when the only error message you get is: bash: echo: write error: Invalid argument Add code to the kernel to implement a new file /sys/fs/resctrl/info/last_cmd_status that provides a more helpful message when a command fails. Commit Id list: 165d3ad884df4b30c3564a478b457b499345886f 29e74f35b2fed0ca3e8b31db157e1d183e9d0819 94457b36e8a5026443707b48dcf54b204e098fd7 9b3a7fd0f5fb583a8fdda678e8a87dff1717f7f3 c377dcfbee808efdb66cf1bb6b9f06fa26b2ad0a cfd0f34e4cd5f1a5ad7000a3104c37886a70bca9 Will be merged into 4.15-rc1 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1714401] Re: [Feature] AEP: ACPI 6.2 - new ACPI label Methods
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1714401 Title: [Feature] AEP: ACPI 6.2 - new ACPI label Methods Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Add support for the _LSI, _LSR, and _LSW methods Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1714401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720045] Re: [Bug] USB 3.1 Gen2 works as 5Gbps
** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720045 Title: [Bug] USB 3.1 Gen2 works as 5Gbps Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: [USB][CFL-S][Mehlow]USB 3.1 Gen2 works as 5Gbps. Steps: 1. boot up platform 2. plug in a USB 3.1 Gen2 device 3. lsusb -t [Expected Results] It will be enumed as 10Gbps device [Observed Results] It is enumed as 10Gbps device. But works after apply 0001-xhci-set-USB3.1-debugging-on-as-default-workaround-m.patch. Target Kernel: 4.14 Target Release: 18.04 If 17.10, it will need back porting To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1720045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715833] Re: [Bug] USB controller failed to respond on Denverton after loading intel_th_pci module
** Changed in: intel
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/1715833
Title:
[Bug] USB controller failed to respond on Denverton after loading
intel_th_pci module
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description:
Ubuntu 17.10 beta 1 login UI hangs up on Denverton. Kernel (v4.12)
boots up with lots of mmc/sdhci error log, we cannot input user name
on Ubuntu login UI via USB keyboard. And we did some bisect work to
address this regression. Finally, we found the following commit
"intel_th: pci: Add Denverton SOC support" which causes this
regression. After reverting this patch based on the upstream kernel
4.13, it can boot up without any mmc/sdhci error log and we can input
the user name via USB keyboard to login successfully.
From 5118ccd34780f4637a9360be580f41f4c1feab48 Mon Sep 17 00:00:00 2001
From: Alexander Shishkin
Date: Tue, 8 Sep 2015 14:03:55 +0300
Subject: [PATCH] intel_th: pci: Add Denverton SOC support
This adds Intel(R) Trace Hub PCI ID for Denverton SOC.
Signed-off-by: Alexander Shishkin
---
drivers/hwtracing/intel_th/pci.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/hwtracing/intel_th/pci.c
b/drivers/hwtracing/intel_th/pci.c
index 0bba384..04bd57b 100644
--- a/drivers/hwtracing/intel_th/pci.c
+++ b/drivers/hwtracing/intel_th/pci.c
@@ -85,6 +85,11 @@ static const struct pci_device_id intel_th_pci_id_table[]
= {
PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0xa2a6),
.driver_data = (kernel_ulong_t)0,
},
+ {
+ /* Denverton */
+ PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x19e1),
+ .driver_data = (kernel_ulong_t)0,
+ },
{ 0 },
};
BIOS version: HVLRCRB.86B.B.64.2017.29.3.01.0406.ACV15D47
And after reverting this patch and entering the os, running "lspci -vv" can
list out this pci device ID. Although, I cannot find the ITH enable options in
BIOS like GLK.
00:1f.7 Non-Essential Instrumentation [1300]: Intel Corporation Device 19e1
(rev 11)
Subsystem: Intel Corporation Device 7270
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR-
Target Kernel: 4.14
Target Platform: 17.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1715833/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730599] Re: [Bug] [USB Function][CFL-CNL PCH]Stall Error and USB Transaction Error in trace, Disable of device-initiated U1/U2 failed and rebind failed: -517 during suspend/res
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730599 Title: [Bug] [USB Function][CFL-CNL PCH]Stall Error and USB Transaction Error in trace, Disable of device-initiated U1/U2 failed and rebind failed: -517 during suspend/resume with usb storage. Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Hardware Configuration Board ID :CoffeeLake S UDIMM RVP PCH: CNL, PCH-H BIOS: CNLSFWR1.R00.X088.D51.1706060006 KSC FW1.00 Steps; 1.connect usb keyboard and usb mass storage to usb host. 2.let system enter s4 and resume [Expected Results] There is no error and fail in dmesg and trace. [Observed Results] There is some error and fail in dmesg and trace. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730595] Re: [Feature] [CFL] GPIO support for CFL-S
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730595 Title: [Feature] [CFL] GPIO support for CFL-S Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: CFL-S GPIO is different than in CNL and we need to implement driver to support that. Target Kernel:TBD Target Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730571] Re: [Bug] Perf cannot use Intel PT and LBRs simultaneously at GLM and GLK
69d8bd8aa7d8906a1e922ae884d97f0bd7f1b269 perf intel-pt: Set no_aux_samples for
the tracking event
v4.14-rc1~173^2~32^2~39
91a8c5b840f2da31280e14b6268761cf14033756 perf intel-pt: Always set no branch
for dummy event
v4.14-rc1~173^2~32^2~38
** Tags added: kernel
** Information type changed from Proprietary to Public
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730571
Title:
[Bug] Perf cannot use Intel PT and LBRs simultaneously at GLM and GLK
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
Description:
An earlier kernel patch allowed enabling PT and LBR at the same time on
Goldmont.
commit ccbebba4c6bf ("perf/x86/intel/pt: Bypass PT vs. LBR exclusivity if the
core supports it")
However, users still cannot use Intel PT and LBRs simultaneously.
$ sudo perf record -e cycles,intel_pt//u -b – sleep 1
Error:
PMU Hardware doesn't support sampling/overflow-interrupts.
Commit IDs:
69d8bd8aa7d8906a1e922ae884d97f0bd7f1b269
91a8c5b840f2da31280e14b6268761cf14033756
Target Kernel: 4.14
Target Release: 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730571/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730571] Re: [Bug] Perf cannot use Intel PT and LBRs simultaneously at GLM and GLK
4.15 is now available in Bionic. Marking this Fix Released.
** Changed in: linux (Ubuntu Bionic)
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/1730571
Title:
[Bug] Perf cannot use Intel PT and LBRs simultaneously at GLM and GLK
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
Description:
An earlier kernel patch allowed enabling PT and LBR at the same time on
Goldmont.
commit ccbebba4c6bf ("perf/x86/intel/pt: Bypass PT vs. LBR exclusivity if the
core supports it")
However, users still cannot use Intel PT and LBRs simultaneously.
$ sudo perf record -e cycles,intel_pt//u -b – sleep 1
Error:
PMU Hardware doesn't support sampling/overflow-interrupts.
Commit IDs:
69d8bd8aa7d8906a1e922ae884d97f0bd7f1b269
91a8c5b840f2da31280e14b6268761cf14033756
Target Kernel: 4.14
Target Release: 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730571/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730788] Re: [Feature][DVN]Denverton SPI-NOR support
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730788 Title: [Feature][DVN]Denverton SPI-NOR support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Add SPI-NOR support for Denverton. Support requested by Customer. Commit Ids:fe602838a66d34f3d1de71feab92b403e244db8c Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730788] Re: [Feature][DVN]Denverton SPI-NOR support
fe602838a66d34f3d1de71feab92b403e244db8c mtd: spi-nor: intel-spi: Add support for Intel Denverton SPI serial flash controller v4.14-rc1~73^2~1^2~6 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730788 Title: [Feature][DVN]Denverton SPI-NOR support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Add SPI-NOR support for Denverton. Support requested by Customer. Commit Ids:fe602838a66d34f3d1de71feab92b403e244db8c Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730782] Re: [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL
** Tags added: kernel ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730782 Title: [Bug] [KNL] ~5x slowdown of application when attaching by perf on KNL Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Workload slows down for default sampling cycles in KNL. There are some processing in perf that's single threaded and bottlenecked when number of cores really go up. A second issue is that things slow down when we issue perf record – workload vs perf record -a – workload Patch is submitted for review https://www.spinics.net/lists/kernel/msg2552460.html https://www.spinics.net/lists/kernel/msg2552461.html https://www.spinics.net/lists/kernel/msg2552462.html https://www.spinics.net/lists/kernel/msg2552463.html Target kernel: TBD Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730814] Re: [Bug] Crystal Ridge - BTT warning/error/bug cleanup
4.15 is now available in Bionic. Marking this Fix Released. ** Changed in: linux (Ubuntu Bionic) 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/1730814 Title: [Bug] Crystal Ridge - BTT warning/error/bug cleanup Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Convert WARN* to dev_WARN*, use dev_warn_ratelimited for IO path, and remove unnecessary BUG_ONs Commit Ids: 86652d2eb347080a991968c9d68708dc010ac56c Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730805] Re: [Feature][Crystal Ridge] Export the read-modify-write boundary in sysfs
a15797f4bef201544263ef5c264c3f48d78cc5d4 libnvdimm, nfit: export an 'ecc_unit_size' sysfs attribute v4.14-rc1~61^2~14 ** Tags added: kernel ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730805 Title: [Feature][Crystal Ridge] Export the read-modify-write boundary in sysfs Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: When the nfit driver initializes it runs an ARS (Address Range Scrub) operation across every pmem range. Part of that process involves determining the ARS capabilities of a given address range. One of the capabilities that is reported is the 'Clear Uncorrectable Error Range Length Unit Size' (see: ACPI 6.2 section 9.20.7.4 Function Index 1 - Query ARS Capabilities). This property is of interest to userspace software as it indicates the boundary at which the NVDIMM may ned to perform read-modify-write cycles to maintain ECC blocks. Commit Ids: a15797f4bef2 Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730829] Re: [Feature]Crystal Ridge:add support for the platform capabilities NFIT sub-table in ACPI 6.2A
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730829 Title: [Feature]Crystal Ridge:add support for the platform capabilities NFIT sub-table in ACPI 6.2A Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Enable support for: "5.2.25.9 Platform Capabilities Structure" in ACPI 6.2A. This involves NFIT driver changes for the new table, and then detecting if the platform has cache flush on fail support. If it does, plumb that through as a region property so that we can pick the proper default to pass to the dax_write_cache() call in pmem_attach_disk(). Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730814] Re: [Bug] Crystal Ridge - BTT warning/error/bug cleanup
86652d2eb347080a991968c9d68708dc010ac56c libnvdimm, btt: clean up warning and error messages v4.14-rc1~61^2~1 ** Tags added: kernel ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730814 Title: [Bug] Crystal Ridge - BTT warning/error/bug cleanup Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Convert WARN* to dev_WARN*, use dev_warn_ratelimited for IO path, and remove unnecessary BUG_ONs Commit Ids: 86652d2eb347080a991968c9d68708dc010ac56c Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730805] Re: [Feature][Crystal Ridge] Export the read-modify-write boundary in sysfs
4.15 is now available in Bionic. Marking this Fix Released. ** Changed in: linux (Ubuntu Bionic) 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/1730805 Title: [Feature][Crystal Ridge] Export the read-modify-write boundary in sysfs Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: When the nfit driver initializes it runs an ARS (Address Range Scrub) operation across every pmem range. Part of that process involves determining the ARS capabilities of a given address range. One of the capabilities that is reported is the 'Clear Uncorrectable Error Range Length Unit Size' (see: ACPI 6.2 section 9.20.7.4 Function Index 1 - Query ARS Capabilities). This property is of interest to userspace software as it indicates the boundary at which the NVDIMM may ned to perform read-modify-write cycles to maintain ECC blocks. Commit Ids: a15797f4bef2 Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730791] Re: [Feature][SKL]Lewisburg PCH GPIO driver
4.15 is now available in Bionic. Marking this Fix Released. ** Changed in: linux (Ubuntu Bionic) 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/1730791 Title: [Feature][SKL]Lewisburg PCH GPIO driver Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: There is a customer request having driver for the GPIO block in Lewisburg PCH. Commit Ids: e480b745386e3911c45e5b281f3471c7aff8cc3b Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730792] Re: [Feature][SKL] Support disabling AVX-512
0b00de857a648dafe7020878c7a27cf776f5edf4 x86/cpuid: Add generic table for CPUID dependencies v4.15-rc1~157^2~50^2~7 0c2a3913d6f50503f7c59d83a6219e39508cc898 x86/fpu: Parse clearcpuid= as early XSAVE argument v4.15-rc1~157^2~50^2~6 57b8b1a1856adaa849d02d547411a553a531022b x86/cpuid: Prevent out of bound access in do_clear_cpu_cap() v4.15-rc1~157^2~50^2~3 73e3a7d2a7c3be29a5a22b85026f6cfa5664267f x86/fpu: Remove the explicit clearing of XSAVE dependent features v4.15-rc1~157^2~50^2~4 cbe96375025e14fc76f9ed42ee5225120d7210f8 bitops: Add clear/set_bit32() to linux/bitops.h v4.15-rc1~157^2~50^2~8 ccb18db2ab9d923df07e7495123fe5fb02329713 x86/fpu: Make XSAVE check the base CPUID features before enabling v4.15-rc1~157^2~50^2~5 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730792 Title: [Feature][SKL] Support disabling AVX-512 Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: On Skylake server we have some problems with AVX512/AVX2 lowering frequency and potentially lowering performance. To do easy debug and as a potential solution it is useful to be able to disable AVX512 and AVX2 I posted patches to disable AVX512/2 at the kernel level. Once they are merged we should back port them ASAP to server oriented distros, so that any issues on SKX deployment can be addressed. Current patches are here https://patchwork.kernel.org/patch/9618881/ https://patchwork.kernel.org/patch/9618883/ Note for backporting: the FPU code has been recently re-organized. So some of the patches likely need to be moved to other files and potentially other functions. But it's straight forward, so shouldn't be too difficult. Commit Ids: 0b00de857a648dafe7020878c7a27cf776f5edf4 0c2a3913d6f50503f7c59d83a6219e39508cc898 57b8b1a1856adaa849d02d547411a553a531022b 73e3a7d2a7c3be29a5a22b85026f6cfa5664267f cbe96375025e14fc76f9ed42ee5225120d7210f8 ccb18db2ab9d923df07e7495123fe5fb02329713 Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730791] Re: [Feature][SKL]Lewisburg PCH GPIO driver
e480b745386e3911c45e5b281f3471c7aff8cc3b pinctrl: intel: Add Intel Lewisburg GPIO support v4.14-rc1~142^2~17 ** Tags added: kernel ** Changed in: intel Status: New => Fix Released ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730791 Title: [Feature][SKL]Lewisburg PCH GPIO driver Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: There is a customer request having driver for the GPIO block in Lewisburg PCH. Commit Ids: e480b745386e3911c45e5b281f3471c7aff8cc3b Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730792] Re: [Feature][SKL] Support disabling AVX-512
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730792 Title: [Feature][SKL] Support disabling AVX-512 Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: On Skylake server we have some problems with AVX512/AVX2 lowering frequency and potentially lowering performance. To do easy debug and as a potential solution it is useful to be able to disable AVX512 and AVX2 I posted patches to disable AVX512/2 at the kernel level. Once they are merged we should back port them ASAP to server oriented distros, so that any issues on SKX deployment can be addressed. Current patches are here https://patchwork.kernel.org/patch/9618881/ https://patchwork.kernel.org/patch/9618883/ Note for backporting: the FPU code has been recently re-organized. So some of the patches likely need to be moved to other files and potentially other functions. But it's straight forward, so shouldn't be too difficult. Commit Ids: 0b00de857a648dafe7020878c7a27cf776f5edf4 0c2a3913d6f50503f7c59d83a6219e39508cc898 57b8b1a1856adaa849d02d547411a553a531022b 73e3a7d2a7c3be29a5a22b85026f6cfa5664267f cbe96375025e14fc76f9ed42ee5225120d7210f8 ccb18db2ab9d923df07e7495123fe5fb02329713 Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730833] Re: [Feature] Lewisburg SPI-NOR driver
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Released ** Changed in: intel Status: New => Fix Released ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730833 Title: [Feature] Lewisburg SPI-NOR driver Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description Add Lewisburg (Purley) PCI ID to the SPI-NOR driver. Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730838] Re: [Bug] The refactored sb_edac failed to be loaded on one 2-socket Haswell machine
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730838 Title: [Bug] The refactored sb_edac failed to be loaded on one 2-socket Haswell machine Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description Red Hat reported one issue that v4.13-rc3 sb_edac failed to be loaded on one of their 2-socket Haswell machine. Log: [ 15.620633] EDAC sbridge: Some needed devices are missing [ 15.632107] EDAC MC: Removed device 0 for sb_edac.c Haswell SrcID#0_Ha#0: DEV :7f:12.0 [ 15.641080] EDAC MC: Removed device 1 for sb_edac.c Haswell SrcID#1_Ha#0: DEV :ff:12.0 [ 15.641125] EDAC sbridge: Couldn't find mci handler [ 15.646583] EDAC sbridge: Couldn't find mci handler [ 15.646587] EDAC sbridge: Failed to register device with error -19. Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730840] Re: [Feature] Break up long walk of wait queue during wake up
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730840 Title: [Feature] Break up long walk of wait queue during wake up Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description In Fujitsu's acceptance test of 8 socket SKX systems, they found that NMI watchdog timer got triggered in wake_up_page_bit function. The cause is the long hold time of the wait queue lock to do the wake ups and traversal of the wait queue. (see LCK-4265) We created a patch series to break up the long traversal of the wait queue in wake_up_page_bit. We bookmark the position in the wait queue after reaching a threshold of wake ups, and release the wait queue lock to allow other tasks blocked a chance to run (e.g. async wake up to remove itself from wake queue in finish_wait). Then we resume from the bookmarked location. This fixes the long spin lock hold time which triggered the watchdog timer. Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730846] Re: [Feature] Crystal Ridge - fix softlockup warnings at NVDIMM namespace init
4.15 is now available in Bionic. Marking this Fix Released. ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730846 Title: [Feature] Crystal Ridge - fix softlockup warnings at NVDIMM namespace init Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: For large capacity NVDIMMs the time it takes to initialize struct page exceeds the default soft lockup timeout. The system is still making forward progress, but we need to add explicit scheduling points to satisfy the watchdog. Commit IDs: 1fdcce6e16c5 9b6e63cbf85b f64ac5e6e306 Target Kernel:4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730848] Re: [Feature] Crystal Ridge - perform dax_device lookup at mount
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Tags added: kernel ** 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/1730848 Title: [Feature] Crystal Ridge - perform dax_device lookup at mount Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: The ->iomap_begin() operation is a hot path, so cache the fs_dax_get_by_host() result at mount time to avoid the incurring the hash lookup overhead on a per-i/o basis. Commit Ids: 26f2f4de0bd9 486aff5e0482 5e405595e5bf 78f354735081 8cf037a8b22f aed9eb1b21e8 Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730847] Re: [Bug] Crystal Ridge - fix ext4 data corruption issues with DAX
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) 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/1730847 Title: [Bug] Crystal Ridge - fix ext4 data corruption issues with DAX Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: There are several existing data corruption level issues that exist with ext4+DAX that happen when S_DAX transitions from one state to another at runtime. Commit Ids: 559db4c6d784 6642586b3e5f 7d3e06a8dae8 8058cac6a1d5 e9072d859df3 Target Kernel:4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730847] Re: [Bug] Crystal Ridge - fix ext4 data corruption issues with DAX
4.15 is now available in Bionic. Marking this 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/1730847 Title: [Bug] Crystal Ridge - fix ext4 data corruption issues with DAX Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: There are several existing data corruption level issues that exist with ext4+DAX that happen when S_DAX transitions from one state to another at runtime. Commit Ids: 559db4c6d784 6642586b3e5f 7d3e06a8dae8 8058cac6a1d5 e9072d859df3 Target Kernel:4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730851] Re: [Feature] Crystal Ridge: DSM v1.6 Support
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730851 Title: [Feature] Crystal Ridge: DSM v1.6 Support Status in intel: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: Description: Add kernel enabling for the new DSM v1.6 commands. This primarily involves teaching the kernel about the new command numbers and revision ids so that we can use the ND_CMD_CALL interface. Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730851] Re: [Feature] Crystal Ridge: DSM v1.6 Support
** Tags removed: bionic ** Tags added: kernel ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1730851 Title: [Feature] Crystal Ridge: DSM v1.6 Support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: Add kernel enabling for the new DSM v1.6 commands. This primarily involves teaching the kernel about the new command numbers and revision ids so that we can use the ND_CMD_CALL interface. Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730867] Re: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation
4.15 is now available in Bionic. Marking this Fix Released. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730867 Title: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation Status in intel: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Description: This is dependent upon these two other Jira features: [HMEM] Specify initial sysfs representation for heterogeneous memory [HMEM] Update QEMU prototype to the latest HMAT spec, R053 This task is to consume the newly updated HMAT talbles and create the sysfs representation. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730867] Re: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation
Sorry, please disregard comment #1. Setting this to Incomplete until we have a set of commit id's to confirm for 18.04. ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: intel 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/1730867 Title: [Feature][HMEM] Consume HMAT tables in Linux guest, create sysfs representation Status in intel: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Description: This is dependent upon these two other Jira features: [HMEM] Specify initial sysfs representation for heterogeneous memory [HMEM] Update QEMU prototype to the latest HMAT spec, R053 This task is to consume the newly updated HMAT talbles and create the sysfs representation. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730887] Re: [Feature] [HMEM] VMA based swap readahead
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) 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/1730887 Title: [Feature] [HMEM] VMA based swap readahead Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description The swap readahead is a important mechanism to reduce the swap in latency. But the original swap readahead algorithm has some issues. a) The original swap readahead algorithm does readahead based on the consecutive blocks in swap device. But the consecutive blocks in swap device just reflect the order of page reclaiming, but don't necessarily reflect the access sequence in RAM. Although for some workloads (such as whole system pure sequential workload), it works, but in general, it doesn't work well for more complex access pattern, such as combined workloads (sequential and random workload runs together) or changing accessing patterns in workload. b) The original swap readahead algorithm just turns random read into sequential read, but doesn’t parallel CPU and disk operations. This can reduce the average latency and the lowest latency, but doesn’t help much for high percentile latency (like 90%, 95%, 99%). To solve the above issues, A VMA based swap readahead algorithm is designed. When the page fault occurs, the pages along the access direction will be checked and the swapped out pages will be readahead if they fall inside the readahead window. There is one readahead window state for each VMA, to reflect the different access patterns for different VMAs. The readahead window is scaled based on whether the accessed page is consecutive in virtual address with the previous accessed page. If so, the readahead window will be extended, otherwise, the readahead window will be shrunk rapidly. Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730882] Re: [Feature] IOMMU Page Request Overflow needs to be cleared
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) 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/1730882 Title: [Feature] IOMMU Page Request Overflow needs to be cleared Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description Currently IOMMU Fault Status register is not clearing Page Request Overflow. Not clearing this would mean any future page-request is going to be automatically dropped by IOMMU. Check section 7.5.1 of the spec. Target Kernel: TBD Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730879] Re: [Feature] Increase percpu counter threshold size
4.15 is now available in Bionic. Marking this Fix Released.
** Tags added: kernel
** Information type changed from Private to Public
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
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/1730879
Title:
[Feature] Increase percpu counter threshold size
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
Description
It was noted that the size of the percpu counters used for
"node/zone_state" is only 8 bytes:
struct per_cpu_pageset {
struct per_cpu_pages pcp;
s8 stat_threshold;
s8 vm_stat_diff[NR_VM_ZONE_STAT_ITEMS];
};
This code is very old. It effectively requires a pair hot, global
cachelines to be touched when the per_cpu counter value does not fit
in "vm_stat_diff".
For this item, we need to increase the size of vm_stat_diff[] from an
s8 to an s16, then allow the ->stat_threshold to be adjusted between
the existing value of 125 and some larger value. Note that the current
threshold from calculate_normal_threshold() is capped at 125 for all
zones over 32GB. We have zones much larger than that today, so it is
likely not scaling optimally.
Target Kernel: 4.14
Target Release: 18.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730879/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730881] Re: [Feature] Support binding swap device to a node
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) 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/1730881 Title: [Feature] Support binding swap device to a node Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description NSG found binding a swap device to a node could improve swap related performance on multi-node system so they would like such feature upstreamed. NSG used to use a previous patch from me that did automatic swap device binding, but that patch requires the swap device has physical node information and works best when swap devices are attached to different node. Systems like EP doesn't have multiple IO hub so multiple swap devices are actually on the same physical node. For this reason, I've then developed a entirely new patch that enables binding swap device to a node, even when 2 swap devices are on the same physical node, they can still be individually bound to 2 different nodes. Target Kernel: 4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742561] Re: [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds
git describe --contains c99d7832dcd7423ba352386107118b9bd8b83158 v4.16-rc1~31^2~21^2~21 commit c99d7832dcd7423ba352386107118b9bd8b83158 Author: Rodrigo Vivi Date: Wed Dec 20 10:29:19 2017 -0800 drm/i915/cfl: Adding more Coffee Lake PCI IDs. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel ** Also affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742561 Title: [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds c99d7832dcd7423ba352386107118b9bd8b83158 (drm branch commit id) (https://patchwork.freedesktop.org/patch/194410/) Target Release: 18.04 Target Kernel: TBD (mainline) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1742561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741391] Re: [Bug] [CFL-S/H][CNL-Y] USB 3.1 UAS is recognized as USB 3.0 device
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Information type changed from Private to Public ** Also affects: linux (Ubuntu Bionic) 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/1741391 Title: [Bug] [CFL-S/H][CNL-Y] USB 3.1 UAS is recognized as USB 3.0 device Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description SW:Linux p-cfls01 4.15.0-rc3 bios:CNLSFWR1.R00.X116.B02.1712090154 on cfls USB 3.1 UAS is recognized as USB 3.0 device. 4.15.0-rc2 works normal. steps 1. insert a USB 3.1 UAS device into USB 3.1 port 2. lsusb -t expected results usb 3.1 is recognized as usb 3.1 device observed results usb 3.1 is recognized as usb 3.0 device HW: CFL Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1741391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU
** Tags added: kernel ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1747134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744638] Re: [Bug] [CNL] mei: LTR holds platform at Pkg C2, cannot enter deeper Pkg C states
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744638 Title: [Bug] [CNL] mei: LTR holds platform at Pkg C2, cannot enter deeper Pkg C states Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Platform: CNL-Y8 LPDDR4 PI (merged rail) RVP with BIOS 108 BIOS configuration: https://wiki.ith.intel.com/pages/viewpage.action?pageId=865050787 At least as far back as the 2017-10-25 Intel Next merge, platform will not go deeper than Pkg C2 when system is idle. Upon further debug, using the pmc_core driver to ignore LTR "6", or bit 6 of LTR_IGN, can allow the system can enter Pkg C8. If I'm not mistaken, according to CSpec bit 6 of LTR_IGN will ignore LTR_ME, which is in the MEI driver's domain. Reproduce by: Boot to text console with latest Intel Next kernel (2017-10-30 as of writing) Run turbostat See residency no deeper than Pkg C2 Expected: At idle, system shows nonzero Pkg C8 residency, or deeper. Actual: At idle, system only shows nonzero Pkg C2 residency. Two work-arounds: echo 6 > /sys/kernel/debug/pmc_core/ltr_ignore Run powertop --auto-tune Criteria for closure: Idle system can enter Pkg C8 (or deeper) without having to explicitly "ignore" LTR 6 or otherwise have to manually enable runtime power management for MEI device(s). Commit ids: Upstream commit, planned to be merged into 4.16 commit cc365dcf0e56271bedf3de95f88922abe248e951 Author: Tomas Winkler Date: Tue Jan 2 12:01:41 2018 +0200 mei: me: allow runtime pm for platform with D0i3 Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1744638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745899] Re: [Bug][KVM][Crystal Ridge] Terrible performance of vNVDIMM on QEMU with device DAX backend
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745899 Title: [Bug][KVM][Crystal Ridge] Terrible performance of vNVDIMM on QEMU with device DAX backend Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: When device DAX (e.g., /dev/daxX.Y) is used as QEMU vNVDIMM backend, its performance in guest is far behind the performance on bare metal. Commit Ids: aa2e063aea79 b8d7044bcff7 (which is in KVM branch instead of mainline kernel) Target kernel:4.16 Target Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1745899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743856] Re: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode)
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743856 Title: EDAC, sb_edac: Backport 1 patch to Ubuntu 17.10 (Fix missing DIMM sysfs entries with KNL SNC2/SNC4 mode) Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: The sb_edac needs additional patch to enable EDAC to know of the existence of some DIMMs attached to channels while figuring out the size of the DIMMs and the cluster mode is SNC2 or SNC4. All the thread connected with this issue is described here https://www.spinics.net/lists/linux-edac/msg08170.html. Please backport the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=24281a2f4ca569d44e44e4cbc500cf08e7bb4c36 to solve the sb_edac driver issue on Ubuntu 17.10. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1743856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744637] Re: [Bug]Crystal Ridge - non-temporal stores receive double fault in KVM guest
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Information type changed from Proprietary to Public ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: 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/1744637 Title: [Bug]Crystal Ridge - non-temporal stores receive double fault in KVM guest Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: I'm seeing a regression in my QEMU based NVDIMM testing system, and I bisected it to this commit: 664f8e26b00c7673a8303b0d40853a0c24ca93e1 is the first bad commit commit 664f8e26b00c7673a8303b0d40853a0c24ca93e1 Author: Wanpeng Li Date: Thu Aug 24 03:35:09 2017 -0700 KVM: X86: Fix loss of exception which has not yet been injected The behavior I'm seeing is that heavy I/O to simulated NVDIMMs in multiple virtual machines causes the QEMU guests to receive double faults, crashing them. Here's an example backtrace: [ 1042.653816] PANIC: double fault, error_code: 0x0 [ 1042.654398] CPU: 2 PID: 30257 Comm: fsstress Not tainted 4.15.0-rc5 #1 [ 1042.655169] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-2.fc27 04/01/2014 [ 1042.656121] RIP: 0010:memcpy_flushcache+0x4d/0x180 [ 1042.656631] RSP: 0018:ac098c7d3808 EFLAGS: 00010286 [ 1042.657245] RAX: ac0d18ca8000 RBX: 0fe0 RCX: ac0d18ca8000 [ 1042.658085] RDX: 921aaa5df000 RSI: 921aaa5e RDI: 19f26e6c9000 [ 1042.658802] RBP: 1000 R08: R09: [ 1042.659503] R10: R11: R12: 921aaa5df020 [ 1042.660306] R13: ac0d18ca8000 R14: f4c102a977c0 R15: 1000 [ 1042.661132] FS: 7f71530b90c0() GS:921b3b28() knlGS: [ 1042.662051] CS: 0010 DS: ES: CR0: 80050033 [ 1042.662528] CR2: 01156002 CR3: 00012a936000 CR4: 06e0 [ 1042.663093] Call Trace: [ 1042.663329] write_pmem+0x6c/0xa0 [nd_pmem] [ 1042.663668] pmem_do_bvec+0x15f/0x330 [nd_pmem] [ 1042.664056] ? kmem_alloc+0x61/0xe0 [xfs] [ 1042.664393] pmem_make_request+0xdd/0x220 [nd_pmem] [ 1042.664781] generic_make_request+0x11f/0x300 [ 1042.665135] ? submit_bio+0x6c/0x140 [ 1042.665436] submit_bio+0x6c/0x140 [ 1042.665754] ? next_bio+0x18/0x40 [ 1042.666025] ? _cond_resched+0x15/0x40 [ 1042.666341] submit_bio_wait+0x53/0x80 [ 1042.666804] blkdev_issue_zeroout+0xdc/0x210 [ 1042.667336] ? __dax_zero_page_range+0xb5/0x140 [ 1042.667810] __dax_zero_page_range+0xb5/0x140 [ 1042.668197] ? xfs_file_iomap_begin+0x2bd/0x8e0 [xfs] [ 1042.668611] iomap_zero_range_actor+0x7c/0x1b0 [ 1042.668974] ? iomap_write_actor+0x170/0x170 [ 1042.669318] iomap_apply+0xa4/0x110 [ 1042.669616] ? iomap_write_actor+0x170/0x170 [ 1042.669958] iomap_zero_range+0x52/0x80 [ 1042.670255] ? iomap_write_actor+0x170/0x170 [ 1042.670616] xfs_setattr_size+0xd4/0x330 [xfs] [ 1042.670995] xfs_ioc_space+0x27e/0x2f0 [xfs] [ 1042.671332] ? terminate_walk+0x87/0xf0 [ 1042.671662] xfs_file_ioctl+0x862/0xa40 [xfs] [ 1042.672035] ? _copy_to_user+0x22/0x30 [ 1042.672346] ? cp_new_stat+0x150/0x180 [ 1042.672663] do_vfs_ioctl+0xa1/0x610 [ 1042.672960] ? SYSC_newfstat+0x3c/0x60 [ 1042.673264] SyS_ioctl+0x74/0x80 [ 1042.673661] entry_SYSCALL_64_fastpath+0x1a/0x7d [ 1042.674239] RIP: 0033:0x7f71525a2dc7 [ 1042.674681] RSP: 002b:7ffef97aa778 EFLAGS: 0246 ORIG_RAX: 0010 [ 1042.675664] RAX: ffda RBX: 000112bc RCX: 7f71525a2dc7 [ 1042.676592] RDX: 7ffef97aa7a0 RSI: 40305825 RDI: 0003 [ 1042.677520] RBP: 0009 R08: 0045 R09: 7ffef97aa78c [ 1042.678442] R10: R11: 0246 R12: 0003 [ 1042.679330] R13: 00019e38 R14: 000fcca7 R15: 0016 [ 1042.680216] Code: 48 8d 5d e0 4c 8d 62 20 48 89 cf 48 29 d7 48 89 de 48 83 e6 e0 4c 01 e6 48 8d 04 17 4c 8b 02 4c 8b 4a 08 4c 8b 52 10 4c 8b 5a 18 <4c> 0f c3 00 4c 0f c3 48 08 4c 0f c3 50 10 4c 0f c3 58 18 48 83 This appears to be independent of both the guest kernel version (this backtrace has v4.15.0-rc5, but I've seen it with other kernels) as well as independent of the host QMEU version (mine happens to be qemu-2.10.1-2.fc27 in Fedora 27). The new behavior is due to this commit being present in the host OS kernel. Prior to this commit I could fire up 4 VMs and run xfstests on my simulated NVDIMMs, but after this commit such testing results
[Kernel-packages] [Bug 1744635] Re: [Bug] Crystal Ridge - Fix 1GB namespace alignment vs misaligned pmem ranges
4.15 is now available in Bionic. Marking this Fix Released. ** Tags added: kernel ** Information type changed from Proprietary to Public ** Changed in: intel Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: 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/1744635 Title: [Bug] Crystal Ridge - Fix 1GB namespace alignment vs misaligned pmem ranges Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: A user reported failure to create a device-dax 1GB aligned namespace: "> On 11/28/2017 10:03 PM, Dan Williams wrote: >> >> # cat /proc/iomem > [..] > 1-186fff : System RAM > 187000-d56fff : Persistent Memory > 187000-d56fff : namespace12.0 > d57000-ed6fff : System RAM > ed7000-1aa6fff : Persistent Memory > ed7000-1aa6fff : namespace13.0 Looks like a kernel bug handling namespace ranges that are misaligned (to the device-dax alignment) at the start and the end of range. These namespaces appear to be 256MB aligned, and the driver fails to trim off the unaligned space when creating the namespace. Thanks for the report, I'll copy you on the fix." Target Kernel:4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1744635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver
** Information type changed from Private to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: intel Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: intel Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730832 Title: [Feature] Add xHCI debug device support in the driver Status in intel: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description xHCI compatible USB host controllers(i.e. super-speed USB3 controllers) can be implemented with the Debug Capability(DbC). It presents a debug device which is fully compliant with the USB framework and provides the equivalent of a very high performance full-duplex serial link. The debug capability operation model and registers interface are defined in 7.6.8 of the xHCI specification, revision 1.1. The DbC debug device shares a root port with the xHCI host. By default, the debug capability is disabled and the root port is assigned to xHCI. When the DbC is enabled, the root port will be assigned to the DbC debug device, and the xHCI sees nothing on this port. This implementation uses a sysfs node named under the xHCI device to manage the enabling and disabling of the debug capability. When the debug capability is enabled, it will present a debug device through the debug port. This debug device is fully compliant with the USB3 framework, and it can be enumerated by a debug host on the other end of the USB link. As soon as the debug device is configured, a TTY serial device named /dev/ttyDBC0 will be created. One use of this link is running a login service on the debug target. Hence it can be remote accessed by a debug host. Another use case can probably be found in servers. It provides a peer-to-peer USB link between two host-only machines. This provides a reasonable out-of-band communication method between two servers. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751714] Re: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751714 Title: [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed) Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: a commit id missed in LP#1685729. [CNL] - New device IDs for CNL v4.16 cb5fda413e1d @Canonical, please take it into 18.04. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1751714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1645969] Re: [Feature] Jefferson Peak(9560) WiFi/BT support
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-firmware (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1645969 Title: [Feature] Jefferson Peak(9560) WiFi/BT support Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux-firmware source package in Bionic: Triaged Bug description: Jefferson Peak (JfP):802.11abgn+acR2 MIMO 2x2 Supports BT 5.0 HW: Gemini Lake Target Release: 18.04 Uptream schedule: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1645969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751724] Re: [Feature] Crystal Ridge-Restrict DAX to configurations with struct page
** Tags added: kernel ** Information type changed from Proprietary to Public ** Changed in: intel Importance: Undecided => Medium ** Changed in: intel Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Medium Status: Triaged ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751724 Title: [Feature] Crystal Ridge-Restrict DAX to configurations with struct page Status in intel: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: Several things break in surprising ways without the "memorypageallocation" property. It's better to assume that DAX is broken/unavailable in that configuration rather than try to explain all the corner cases where operations with a DAX mapping will fail. Disabling DAX support altogether if the pages are not allocated, DAX is mostly unusable without pages. Commit id list: 24f3478d664b 569d0365f571 b4b5798cea8f Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1751724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1686034] Re: [Feature] Thunderbolt: Integrate thunderbolt user space security level components
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686034 Title: [Feature] Thunderbolt: Integrate thunderbolt user space security level components Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: Support security levels for Thunderbolt. This feature allows users to approve devices before being able to use them. Target Kernel: 4.13 Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1686034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713619] Re: [Feature] RDT: Disable most RDT features on Skylake server
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1713619 Title: [Feature] RDT: Disable most RDT features on Skylake server Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Description: There are serious errata in CMT, MBM and CAT sub-features of resource director technology. Disable these features by default on Skylake but provide a boot time argument to re-enable them for users who understand the errata and can use them for specific workloads. Commit IDs:(4.14) 0576113a387e0c8a5d9e24b4cd62605d1c9c0db8 1d9807fc64c131a83a96917f2b2da1c9b00cf127 d56593eb5eda8f593db92927059697bbf89bc4b3 Target Release : 17.10 Target Kernel: 4.14 (Need backporting into 17.10 from 4.14 to 4.13) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1713619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716843] Re: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity, BDW-de/ep/ex,
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716843 Title: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW- de/ep/ex, Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Description: CQM2(CMT/MBM rework) upstream patchset has been merged into upstream in 4.14-rc1. And the patch 5dc1d5c6bac2 (“x86/intel_rdt: Simplify info and base file lists”) fixed this issue by the way in another way with rework. This issue will not happen on 4.14-rc kernel. Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1716843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712031] Re: [Feature] PXE boot with Intel Omni-Path
** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1712031 Title: [Feature] PXE boot with Intel Omni-Path Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Bug description: Description: This is about ability to PXE boot over Intel Fabric. Netboot initrd is missing infiniband kernel stack along with hfi1.ko (for 1st generation of Intel Omni-Path cards). In addition some firmware files required to load modules are also missing in initrd. This firmware came from existing linux-firmware package, but is not included in netboot initrd image. Add Intel Omni-Path Architecture (OPA) Firmware to initrd.gz The initrd.gz supplied on Ubuntu 17.04 is missing the following firmware listed below in the /lib/firmware directory. As a result, PXE boot over fabric fails. hfi1_dc8051.fw hfi1_fabric.fw hfi1_pcie.fw hfi1_sbus.fw Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1712031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591609] Re: [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality Monitoring (CQM)
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591609 Title: [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality Monitoring (CQM) Status in intel: Incomplete Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Google has sent a new cqm patch with a lot of fixes to the existing cqm which is upstream. The MBM was based on the old cqm and now needs to be ported on top of the new version of cqm. The google patch is enormous and hence mbm requires a lot of changes to work on top of it. However This wont impact the openstack usage of cqm/mbm as the name of the events would still be the same and they can just be used like before - only that there may be some features which wernt working will work now. Platform: BDW-EP or BDW-EX upstream schedule: 4.13 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708469] Re: [Hyper-V] Transparent SR-IOV solves bonding race conditions
Per discussion with Microsoft, the backport to the stock Xenial 4.4 kernel is too risky to consider for SRU. Users will need to use the linux-azure kernel for this. The linux-azure kernel has been promoted to -updates so I will mark that task as Fix Released and set the linux task to Won't Fix. Thanks. ** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708469 Title: [Hyper-V] Transparent SR-IOV solves bonding race conditions Status in linux package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: Fix Released Bug description: Description of problem: Because of Azure provisioning of VF interfaces taking several seconds after boot, a number of race conditions were found in testing. By putting the effect of SR-IOV bonding into netvsc we avoid these race conditions. Upstream commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=f6775a28c43375945ba39581bdf8e90d0061f350 (because of merge requirements, there may be other dependencies that need to be merged, even for linux-azure's 4.11+ base for Hyper-V) Background In Hyper-V SR-IOV can be enabled (and disabled) by changing guest settings on host. When SR-IOV is enabled a matching PCI device is hot plugged and visible on guest. The VF device is an add-on to an existing netvsc device, and has the same MAC address. How is this different? The original support of VF relied on using bonding driver in active standby mode to handle the VF device. With the new netvsc VF logic, the Linux hyper-V network virtual driver will directly manage the link to SR-IOV VF device. When VF device is detected (hot plug) it is automatically made a slave device of the netvsc device. The VF device state reflects the state of the netvsc device; i.e. if netvsc is set down, then VF is set down. If netvsc is set up, then VF is brought up. Packet flow is independent of VF status; all packets are sent and received as if they were associated with the netvsc device. If VF is removed or link is down then the synthetic VMBUS path is used. What was wrong with using bonding script? A lot of work went into getting the bonding script to work on all distributions, but it was a major struggle. Linux network devices can be configured many, many ways and there is no one solution from userspace to make it all work. What is really hard is when configuration is attached to synthetic device during boot (eth0) and then the same addresses and firewall rules needs to also work later if doing bonding. The new code gets around all of this. How does VF work during initialization? Since all packets are sent and received through the logical netvsc device, initialization is much easier. Just configure the regular netvsc Ethernet device; when/if SR-IOV is enabled it just works. Provisioning and cloud init only need to worry about setting up netvsc device (eth0). If SR-IOV is enabled (even as a later step), the address and rules stay the same. What devices show up? Both netvsc and PCI devices are visible in the system. The netvsc device is active and named in usual manner (eth0). The PCI device is visible to Linux and gets renamed by udev to a persistent name (enP2p3s0). The PCI device name is now irrelevant now. The logic also sets the PCI VF device SLAVE flag on the network device so network tools can see the relationship if they are smart enough to understand how layered devices work. This is a lot like how I see Windows working. The VF device is visible in Device Manager, but is not configured. Is there any performance impact? There is no visible change in performance. The bonding and netvsc driver both have equivalent steps. Is it compatible with old bonding script? It turns out that if you use the old bonding script, then everything still works but in a sub-optimum manner. The previous bonding script package can be deprecated when this kernel patch is present. What if I add address or firewall rule onto the VF? Same problems occur with now as already occur with bonding, bridging, teaming on Linux if user incorrectly does configuration onto an underlying slave device. It will sort of work, packets will come in and out but the Linux kernel gets confused and things like ARP don’t work right. There is no way to block manipulation of the slave device, and I am sure someone will find some special use case where they want it. How reproducible: A discussion of potential race conditions with the bonding script can be had, but this change gets past that behavior. Please work with Microsoft on reproduction scenarios. Steps to Reproduce: 1. Configure a VM in Azur
[Kernel-packages] [Bug 1709257] Re: [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping Harrisonville SDP
** 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/1709257 Title: [Bug] Harrisonville: pnd2_edac always fail to load on B1 stepping Harrisonville SDP Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: During our EDAC validation on Wind River Linux 9, we found pnd2_edac manually load always fails on B1 stepping Harrisonville SDP. Error info as below: root@intel-x86-64:~# uname -r 4.8.20-WR9.0.0.5_standard root@intel-x86-64:~# dmesg |grep -i edac [ 11.949838] EDAC MC: Ver: 3.0.0 [ 11.954312] EDAC DEBUG: edac_mc_sysfs_init: device mc created [ 12.060157] EDAC DEBUG: pnd2_init: [ 12.060160] EDAC DEBUG: pnd2_probe: [ 12.060167] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000 [ 12.060169] EDAC DEBUG: dnv_rd_reg: Read b_cr_touud_lo_pci=_8000 [ 12.060172] EDAC DEBUG: dnv_rd_reg: Read b_cr_touud_hi_pci=_0004 [ 12.060228] EDAC DEBUG: dnv_rd_reg: Read b_cr_asym_mem_region0_mchbar=_ [ 12.060239] EDAC DEBUG: dnv_rd_reg: Read b_cr_asym_mem_region1_mchbar=_ [ 12.060247] EDAC DEBUG: dnv_rd_reg: Read b_cr_mot_out_base_mchbar=_ [ 12.060255] EDAC DEBUG: dnv_rd_reg: Read b_cr_mot_out_mask_mchbar=_ [ 12.078301] Modules linked in: pnd2_edac(+) edac_core x86_pkg_temp_thermal i2c_i801 intel_powerclamp matroxfb_base matroxfb_g450 matroxfb_accel matroxfb_DAC1064 g450_pll matroxfb_misc i2c_ismt i2c_smbus coretemp crct10dif_pclmul crct10dif_common aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd efi_pstore efivars acpi_cpufreq tpm_tis tpm_tis_core softdog efivarfs [ 12.143390] [] ? dnv_rd_reg+0x128/0x220 [pnd2_edac] [ 12.148890] [] dnv_rd_reg+0x128/0x220 [pnd2_edac] [ 12.148896] [] pnd2_init+0x22b/0x809 [pnd2_edac] [ 12.148961] EDAC pnd2: Failed to register device with error -19. [ 12.180813] EDAC DEBUG: pnd2_init: [ 12.180814] EDAC DEBUG: pnd2_probe: [ 12.180841] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000 [ 12.180937] EDAC DEBUG: dnv_rd_reg: Read b_cr_touud_lo_pci=_8000 [ 12.180969] EDAC DEBUG: dnv_rd_reg: Read b_cr_touud_hi_pci=_0004 [ 12.181129] EDAC DEBUG: dnv_rd_reg: Read b_cr_asym_mem_region0_mchbar=_ [ 12.181299] EDAC DEBUG: dnv_rd_reg: Read b_cr_asym_mem_region1_mchbar=_ [ 12.181425] EDAC DEBUG: dnv_rd_reg: Read b_cr_mot_out_base_mchbar=_ [ 12.181671] EDAC DEBUG: dnv_rd_reg: Read b_cr_mot_out_mask_mchbar=_ [ 12.181810] EDAC pnd2: Failed to register device with error -19. root@intel-x86-64:~# dmesg -c > dmesg.clear_14.D91.log root@intel-x86-64:~# modprobe edac_core root@intel-x86-64:~# modprobe pnd2_edac modprobe: ERROR: could not insert 'pnd2_edac': No such device root@intel-x86-64:~# dmesg [ 194.524122] EDAC DEBUG: pnd2_init: [ 194.524126] EDAC DEBUG: pnd2_probe: [ 194.524135] EDAC DEBUG: dnv_rd_reg: Read b_cr_tolud_pci=_8000 [ 194.524139] EDAC DEBUG: dnv_rd_reg: Read b_cr_touud_lo_pci=_8000 [ 194.524143] EDAC DEBUG: dnv_rd_reg: Read b_cr_touud_hi_pci=_0004 [ 194.524211] EDAC DEBUG: dnv_rd_reg: Read b_cr_asym_mem_region0_mchbar=_ [ 194.524226] EDAC DEBUG: dnv_rd_reg: Read b_cr_asym_mem_region1_mchbar=_ [ 194.524239] EDAC DEBUG: dnv_rd_reg: Read b_cr_mot_out_base_mchbar=_ [ 194.524252] EDAC DEBUG: dnv_rd_reg: Read b_cr_mot_out_mask_mchbar=_ [ 194.524264] EDAC pnd2: Failed to register device with error -19. root@intel-x86-64:~# dmidecode -t bios | grep Version Version: HAVLCRB1.X64.0014.D91.1704200405 Target Kernel: 4.14 Target Release: 18.04 if 17.10, it will need back porting To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1709257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712249] Re: [Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning / failure
Marking this Fix Released for Artful 17.10 as it contains a 4.13 based
kernel containing the commit referenced in comment #1.
$ git describe --contains bbb3be170ac2891526ad07b18af7db226879a8e7
v4.13~241^2
commit bbb3be170ac2891526ad07b18af7db226879a8e7
Author: Dan Williams
Date: Tue Jul 18 17:49:14 2017 -0700
device-dax: fix sysfs duplicate warnings
** Changed in: linux (Ubuntu Artful)
Status: In Progress => 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/1712249
Title:
[Bug] Crystal Ridge: Fix device-dax sysfs duplicate name warning /
failure
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Bug description:
Fix warnings of the form...
WARNING: CPU: 10 PID: 4983 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
sysfs: cannot create duplicate filename '/class/dax/dax12.0'
Call Trace:
dump_stack+0x63/0x86
__warn+0xcb/0xf0
warn_slowpath_fmt+0x5a/0x80
? kernfs_path_from_node+0x4f/0x60
sysfs_warn_dup+0x62/0x80
sysfs_do_create_link_sd.isra.2+0x97/0xb0
sysfs_create_link+0x25/0x40
device_add+0x266/0x630
devm_create_dax_dev+0x2cf/0x340 [dax]
dax_pmem_probe+0x1f5/0x26e [dax_pmem]
nvdimm_bus_probe+0x71/0x120
...by reusing the namespace id for the device-dax instance name.
Now that we have decided that there will never by more than one
device-dax instance per libnvdimm-namespace parent device [1], we can
directly reuse the namepace ids. There are some possible follow-on
cleanups, but those are saved for a later patch to simplify the -stable
backport.
[1]: https://lists.01.org/pipermail/linux-nvdimm/2016-December/008266.html
Fixes: 98a29c39dc68 ("libnvdimm, namespace: allow creation of multiple
pmem...")
Cc: Jeff Moyer
Cc:
Reported-by: Dariusz Dokupil
Signed-off-by: Dan Williams
Target Release: 17.10
Target Kernel: 4.13
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1712249/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715578] Re: [Patch] network-i40e:NVM bug fixes (cherrypick from 4.14)
** 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/1715578
Title:
[Patch] network-i40e:NVM bug fixes (cherrypick from 4.14)
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Description:
Theses two commits need to be cherrypicked from upstream to 4.12/4.13 and
integrated into 17.10
Target Kernel: 4.14
Target Release: 17.10
Action: Cherrypick
Here are the two commit id's:
commit 3c8f3e96af3a6799841761923d000566645f0942
Author: Jacob Keller
Date: Fri Sep 1 13:43:08 2017 -0700
i40e: point wb_desc at the nvm_wb_desc during i40e_read_nvm_aq
When introducing the functions to read the NVM through the AdminQ,
we
did not correctly mark the wb_desc.
Fixes: 7073f46e443e ("i40e: Add AQ commands for NVM Update for
X722", 2015-06-05)
Signed-off-by: Jacob Keller
Tested-by: Andrew Bowers
Signed-off-by: Jeff Kirsher
commit 09f79fd49d94cda5837e9bfd0cb32b3b6d9f
Author: Anjali Singhai Jain
Date: Fri Sep 1 13:42:49 2017 -0700
i40e: avoid NVM acquire deadlock during NVM update
X722 devices use the AdminQ to access the NVM, and this requires
taking
the AdminQ lock. Because of this, we lock the AdminQ during
i40e_read_nvm(), which is also called in places where the lock is
already held, such as the firmware update path which wants to lock
once
and then unlock when finished after performing several tasks.
Although this should have only affected X722 devices, commit
96a39aed25e6 ("i40e: Acquire NVM lock before reads on all devices",
2016-12-02) added locking for all NVM reads, regardless of device
family.
This resulted in us accidentally causing NVM acquire timeouts on
all
devices, causing failed firmware updates which left the eeprom in
a corrupt state.
Create unsafe non-locked variants of i40e_read_nvm_word and
i40e_read_nvm_buffer, __i40e_read_nvm_word and
__i40e_read_nvm_buffer
respectively. These variants will not take the NVM lock and are
expected
to only be called in places where the NVM lock is already held if
needed.
Since the only caller of i40e_read_nvm_buffer() was in such a path,
remove it entirely in favor of the unsafe version. If necessary we
can
always add it back in the future.
Additionally, we now need to hold the NVM lock in
i40e_validate_checksum
because the call to i40e_calc_nvm_checksum now assumes that the NVM
lock
is held. We can further move the call to read
I40E_SR_SW_CHECKSUM_WORD
up a bit so that we do not need to acquire the NVM lock twice.
This should resolve firmware updates and also fix potential raise
that
could have caused the driver to report an invalid NVM checksum upon
driver load.
Reported-by: Stefan Assmann
Fixes: 96a39aed25e6 ("i40e: Acquire NVM lock before reads on all
devices", 2016-12-02)
Signed-off-by: Anjali Singhai Jain
Signed-off-by: Jacob Keller
Tested-by: Andrew Bowers
Signed-off-by: Jeff Kirsher
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1715578/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704439] Re: [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
** 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/1704439 Title: [Feature] Crystal Ridge - have 4k DAX faults use a common zero page Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description - Move the DAX 4k zero page handling to use a single 4k zero page instead of allocating pages on demand. This will mirror the way that things are done for the 2 MiB case, and will reduce the amount of memory we use when reading 4k holes in DAX. Target Kernel:4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716843] Re: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity, BDW-de/ep/ex,
** 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/1716843 Title: [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW- de/ep/ex, Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: CQM2(CMT/MBM rework) upstream patchset has been merged into upstream in 4.14-rc1. And the patch 5dc1d5c6bac2 (“x86/intel_rdt: Simplify info and base file lists”) fixed this issue by the way in another way with rework. This issue will not happen on 4.14-rc kernel. Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1716843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1717430] Re: [Bug] Thunderbolt-patches: Related to the way the key for secure connection is handled
** 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/1717430 Title: [Bug] Thunderbolt-patches: Related to the way the key for secure connection is handled Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: . These patches allow security-related (preventing non-root users from reading the key) and functional capability (not blocking “connect once” flow). Merged in kernel v 4.14 8fdd6ab36197 thunderbolt: Remove superfluous check – Needed to enable Allow clearing key e545f0d8a54a thunderbolt: Allow clearing the key – user cannot reset the device key, without disconnecting device 0956e4116922 thunderbolt: Make key root-only accessible – security, non-root users can read the key, possible security breach Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1717430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1717431] Re: [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI calls w.r.t. PCI enumeration
** 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/1717431 Title: [Bug] Thunderbolt-patches: Fixes the issue regarding the order of ACPI calls w.r.t. PCI enumeration Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: Without these patches, TBT device that is connected on boot is usually not functional. Only reconnecting after OS up works. This is a serious usability issue. Merged in kernel v 4.14 ecc1165b8b74 ACPICA: Dispatch active GPEs at init time 1312b7e0caca ACPICA: Make it possible to enable runtime GPEs earlier eb7f43c4adb4 ACPI / scan: Enable GPEs before scanning the namespace Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1717431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704350] Re: [Feature] Crystal Ridge - BTT - Rework error clearing
** 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/1704350 Title: [Feature] Crystal Ridge - BTT - Rework error clearing Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: Clearing errors in the IO path in the BTT is not feasible, as the acpi DSM path can also sleep. Move the error clearing out of the IO path, to before putting a block on the free list. Also investigate using the map error bit to persist error information in BTT metadata. Target Kernel:4.14 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720045] Re: [Bug] USB 3.1 Gen2 works as 5Gbps
** Changed in: intel 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/1720045 Title: [Bug] USB 3.1 Gen2 works as 5Gbps Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Description: [USB][CFL-S][Mehlow]USB 3.1 Gen2 works as 5Gbps. Steps: 1. boot up platform 2. plug in a USB 3.1 Gen2 device 3. lsusb -t [Expected Results] It will be enumed as 10Gbps device [Observed Results] It is enumed as 10Gbps device. But works after apply 0001-xhci-set-USB3.1-debugging-on-as-default-workaround-m.patch. Target Kernel: 4.14 Target Release: 18.04 If 17.10, it will need back porting To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1720045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1713619] Re: [Feature] RDT: Disable most RDT features on Skylake server
** Changed in: intel 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/1713619 Title: [Feature] RDT: Disable most RDT features on Skylake server Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Description: There are serious errata in CMT, MBM and CAT sub-features of resource director technology. Disable these features by default on Skylake but provide a boot time argument to re-enable them for users who understand the errata and can use them for specific workloads. Commit IDs:(4.14) 0576113a387e0c8a5d9e24b4cd62605d1c9c0db8 1d9807fc64c131a83a96917f2b2da1c9b00cf127 d56593eb5eda8f593db92927059697bbf89bc4b3 Target Release : 17.10 Target Kernel: 4.14 (Need backporting into 17.10 from 4.14 to 4.13) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1713619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591813] Re: [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
** 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/1591813 Title: [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: On SKX PEBS bits should report whether a memory address DLA sample is crystal ridge: hey have two PEBS encodings for L4_HIT Local and L4_HIT Remote. Since we have no L4, we setup the PRE for Server so that the PRE encodings that map onto L4_HIT are actually crystal ridge. So PEBS 0x8 (L4 HIT Local) should mean serviced by local crystal ridge memory on a SKX part, and PEBS 0x9 (L4 HIT Remote) should mean serviced by remote crystal ridge memory on a SKX part. That said, there are multiple steps in the chain that gets that information from the memory controller to the core, and I don't think any of those steps has been formally validated. We need to extend perf to report these distinctions. First needs some testing if it actually works. Would require kernel changes, ABI changes, perf report changes. HW: Purley Upstream schedule: kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591829] Re: [featue] GPIO support for Denverton
** Changed in: intel 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/1591829 Title: [featue] GPIO support for Denverton Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Denverton has similar GPIO block than Broxton. This needs to be enabled in some customer setups. HW: Harrisonvile Upstream schedule: Kernel: 4.14 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591609] Re: [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality Monitoring (CQM)
** Changed in: intel 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/1591609 Title: [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality Monitoring (CQM) Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Google has sent a new cqm patch with a lot of fixes to the existing cqm which is upstream. The MBM was based on the old cqm and now needs to be ported on top of the new version of cqm. The google patch is enormous and hence mbm requires a lot of changes to work on top of it. However This wont impact the openstack usage of cqm/mbm as the name of the events would still be the same and they can just be used like before - only that there may be some features which wernt working will work now. Platform: BDW-EP or BDW-EX upstream schedule: 4.13 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712709] Re: [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.
** Changed in: linux (Ubuntu Artful) Status: In Progress => 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/1712709 Title: [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365. Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: This jira is to track the commits for making suspend to idle function on Dell 9360 and Dell 9365. 0ce3fcaff92908c370334ce3b9111aeea71159d6 33e4f80ee69b5168badf37edbfed796eb48434b9 76380636280b46541a9d2fe5aac497475bfbcde8 8110dd281e155e5010ffd657bba4742ebef7a93f 880a66275ef4d1e08e5d4dcf4cec768de18c68ef c7b5a4e6e8fbef8fdf2c529f953000d24c561339 eed4d47efe9508b855b09754cf6de4325d8a2f0d f3b7eaae1b35eb8077610eb7c7db042c9b0645e1 Target Kernel: 4.13 Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1712709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1712232] Re: [Feature] KNM: KNM NIs Enabling
** 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/1712232 Title: [Feature] KNM: KNM NIs Enabling Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Status in qemu source package in Artful: Fix Released Bug description: KNM NIs Enabling, including avx512 4vnniw, 4fmaps, vpopcntdq AVX512_4VNNIW and AVX512_4FMAPS Linux kernel commit id: 4504b5c9414c55da37f26b1faf49c09a2acbf255 QEMU commit id: 95ea69fb46266aaa46d0c8b7f0ba8c4903dbe4e3 AVX512_VPOPCNTDQ QEMU commit id: f77543772dcd38fa438470d9b80bafbd3a3ebbd7 This feature should have been merged to 17.10 beta1. Create it for track. Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1712232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704325] Re: [Feature] Crystal Ridge - 4.12 - dax_device + dax_operations
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) 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/1704325 Title: [Feature] Crystal Ridge - 4.12 - dax_device + dax_operations Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: Introduce 'struct dax_device' and 'struct dax_operations': Prompted by a request from Linus and feedback from Christoph this allows for dax capable drivers to publish their own custom dax operations. This fixes the broken assumption that all dax operations are related to a persistent memory device, and makes it easier for other architectures and platforms to add customized persistent memory support. Target Kernel:4.12 Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704326] Re: [Bug] Crystal Ridge - 4.12 - Clear errors when initializing a new metadata layout
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) 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/1704326 Title: [Bug] Crystal Ridge - 4.12 - Clear errors when initializing a new metadata layout Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: Description: If we had badblocks/poison in the metadata area of a BTT, recreating the BTT would not clear the poison in all cases, notably the flog area. This is because rw_bytes will only clear errors if the request being sent down is 512B aligned and sized. Make sure that when writing the map and info blocks, the rw_bytes being sent are of the correct size/alignment. For the flog, instead of doing the smaller log_entry writes only, first do a 'wipe' of the entire area by writing zeroes in large enough chunks so that errors get cleared. Target Kernel:4.12 Target Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1704326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
