[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-08-10 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.11.0-13.19

---
linux (4.11.0-13.19) artful; urgency=low

  * CVE-2017-7533
- dentry name snapshots

linux (4.11.0-12.18) artful; urgency=low

  * linux: 4.11.0-12.18 -proposed tracker (LP: #1707635)
- no change rebuild to pick up the new binutils.

  * Adt tests of src:linux time out often on armhf lxc containers (LP: #1705495)
- [Packaging] tests -- reduce rebuild test to one flavour
- [Packaging] tests -- reduce rebuild test to one flavour -- use filter

  * [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y (LP: #1706141)
- [Config] set EDAC_MM_EDAC=y for ARM64

  * [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing
(LP: #1690174)
- hv_netvsc: Exclude non-TCP port numbers from vRSS hashing

  * ath10k doesn't report full RSSI information (LP: #1706531)
- ath10k: add per chain RSSI reporting

  * ideapad_laptop don't support v310-14isk (LP: #1705378)
- platform/x86: ideapad-laptop: Add several models to no_hw_rfkill

  * Ubuntu 16.04.3: Qemu fails on P9 (LP: #1686019)
- KVM: PPC: Pass kvm* to kvmppc_find_table()
- KVM: PPC: Use preregistered memory API to access TCE list
- KVM: PPC: VFIO: Add in-kernel acceleration for VFIO
- powerpc/powernv/iommu: Add real mode version of 
iommu_table_ops::exchange()
- powerpc/iommu/vfio_spapr_tce: Cleanup iommu_table disposal
- powerpc/vfio_spapr_tce: Add reference counting to iommu_table
- powerpc/mmu: Add real mode support for IOMMU preregistered memory
- KVM: PPC: Reserve KVM_CAP_SPAPR_TCE_VFIO capability number
- KVM: PPC: Book3S HV: Add radix checks in real-mode hypercall handlers

  * hns: ethtool selftest crashes system (LP: #1705712)
- net/hns:bugfix of ethtool -t phy self_test

  * ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on
(LP: #1673564)
- KVM: arm/arm64: vgic-v3: Use PREbits to infer the number of ICH_APxRn_EL2
  registers
- KVM: arm/arm64: vgic-v3: Fix nr_pre_bits bitfield extraction
- arm64: Add a facility to turn an ESR syndrome into a sysreg encoding
- KVM: arm/arm64: vgic-v3: Add accessors for the ICH_APxRn_EL2 registers
- KVM: arm64: Make kvm_condition_valid32() accessible from EL2
- KVM: arm64: vgic-v3: Add hook to handle guest GICv3 sysreg accesses at EL2
- KVM: arm64: vgic-v3: Add ICV_BPR1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_IGRPEN1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_IAR1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_EOIR1_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_AP1Rn_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_HPPIR1_EL1 handler
- KVM: arm64: vgic-v3: Enable trapping of Group-1 system registers
- KVM: arm64: Enable GICv3 Group-1 sysreg trapping via command-line
- KVM: arm64: vgic-v3: Add ICV_BPR0_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_IGNREN0_EL1 handler
- KVM: arm64: vgic-v3: Add misc Group-0 handlers
- KVM: arm64: vgic-v3: Enable trapping of Group-0 system registers
- KVM: arm64: Enable GICv3 Group-0 sysreg trapping via command-line
- arm64: Add MIDR values for Cavium cn83XX SoCs
- arm64: Add workaround for Cavium Thunder erratum 30115
- KVM: arm64: vgic-v3: Add ICV_DIR_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_RPR_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_CTLR_EL1 handler
- KVM: arm64: vgic-v3: Add ICV_PMR_EL1 handler
- KVM: arm64: Enable GICv3 common sysreg trapping via command-line
- KVM: arm64: vgic-v3: Log which GICv3 system registers are trapped
- arm64: KVM: Make unexpected reads from WO registers inject an undef
- KVM: arm64: Log an error if trapping a read-from-write-only GICv3 access
- KVM: arm64: Log an error if trapping a write-to-read-only GICv3 access

  * ath9k freezes suspend resume Ubuntu 17.04 (LP: #1697027)
- ath9k: fix an invalid pointer dereference in ath9k_rng_stop()

  * xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2
comp_code 13 (LP: #1667750)
- xhci: Bad Ethernet performance plugged in ASM1042A host

  * Migrating KSM page causes the VM lock up as the KSM page merging list is too
large (LP: #1680513)
- ksm: introduce ksm_max_page_sharing per page deduplication limit
- ksm: fix use after free with merge_across_nodes = 0
- ksm: cleanup stable_node chain collapse case
- ksm: swap the two output parameters of chain/chain_prune
- ksm: optimize refile of stable_node_dup at the head of the chain

  * Artful update to v4.11.12 stable release (LP: #1706067)
- net/phy: micrel: configure intterupts after autoneg workaround
- ipv6: avoid unregistering inet6_dev for loopback
- netvsc: don't access netdev->num_rx_queues directly
- sfc: Fix MCDI command size for filter operations
- net: account for current skb length when deciding about UFO
- net: dp83640: Avoid NULL pointer dereference.
- tcp: reset sk_rx_dst in

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-08-03 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.10.0-30.34

---
linux (4.10.0-30.34) zesty; urgency=low

  * CVE-2017-7533
- dentry name snapshots

linux (4.10.0-29.33) zesty; urgency=low

  * linux: 4.10.0-29.33 -proposed tracker (LP: #1704961)

  * Opal and POWER9 DD2 (LP: #1702159)
- powerpc/powernv: Tell OPAL about our MMU mode on POWER9
- powerpc/powernv: Fix boot on Power8 bare metal due to 
opal_configure_cores()

  * CVE-2017-1000364
- mm/mmap.c: do not blow on PROT_NONE MAP_FIXED holes in the stack
- mm/mmap.c: expand_downwards: don't require the gap if !vm_prev

  * [Xenial] nvme: Quirks for PM1725 controllers (LP: #1704435)
- nvme: Quirks for PM1725 controllers

  * hns: under heavy load, NIC may fail and require reboot (LP: #1704146)
- net: hns: Bugfix for Tx timeout handling in hns driver

  * New ACPI identifiers for ThunderX SMMU (LP: #1703437)
- iommu/arm-smmu: Plumb in new ACPI identifiers

  * CVE-2017-7482
- rxrpc: Fix several cases where a padded len isn't checked in ticket decode

  * CVE-2017-1000365
- fs/exec.c: account for argv/envp pointers

  * CVE-2017-10810
- drm/virtio: don't leak bo on drm_gem_object_init failure

  * Data corruption with hio driver  (LP: #1701316)
- SAUCE: hio: Fix incorrect use of enum req_opf values

  * arm64: fix crash reading /proc/kcore (LP: #1702749)
- fs/proc: kcore: use kcore_list type to check for vmalloc/module address
- arm64: mm: select CONFIG_ARCH_PROC_KCORE_TEXT

  * cxlflash update request in the Xenial SRU stream (LP: #1702521)
- scsi: cxlflash: Refactor context reset to share reset logic
- scsi: cxlflash: Support SQ Command Mode
- scsi: cxlflash: Cleanup prints
- scsi: cxlflash: Cancel scheduled workers before stopping AFU
- scsi: cxlflash: Enable PCI device ID for future IBM CXL Flash AFU
- scsi: cxlflash: Separate RRQ processing from the RRQ interrupt handler
- scsi: cxlflash: Serialize RRQ access and support offlevel processing
- scsi: cxlflash: Implement IRQ polling for RRQ processing
- scsi: cxlflash: Update sysfs helper routines to pass config structure
- scsi: cxlflash: Support dynamic number of FC ports
- scsi: cxlflash: Remove port configuration assumptions
- scsi: cxlflash: Hide FC internals behind common access routine
- scsi: cxlflash: SISlite updates to support 4 ports
- scsi: cxlflash: Support up to 4 ports
- scsi: cxlflash: Fence EEH during probe
- scsi: cxlflash: Remove unnecessary DMA mapping
- scsi: cxlflash: Fix power-of-two validations
- scsi: cxlflash: Fix warnings/errors
- scsi: cxlflash: Improve asynchronous interrupt processing
- scsi: cxlflash: Support multiple hardware queues
- scsi: cxlflash: Add hardware queues attribute
- scsi: cxlflash: Introduce hardware queue steering
- cxl: Enable PCI device IDs for future IBM CXL adapters
- scsi: cxlflash: Select IRQ_POLL
- scsi: cxlflash: Combine the send queue locks
- scsi: cxlflash: Update cxlflash_afu_sync() to return errno
- scsi: cxlflash: Reset hardware queue context via specified register
- scsi: cxlflash: Schedule asynchronous reset of the host
- scsi: cxlflash: Handle AFU sync failures
- scsi: cxlflash: Track pending scsi commands in each hardware queue
- scsi: cxlflash: Flush pending commands in cleanup path
- scsi: cxlflash: Add scsi command abort handler
- scsi: cxlflash: Create character device to provide host management 
interface
- scsi: cxlflash: Separate AFU internal command handling from AFU sync
  specifics
- scsi: cxlflash: Introduce host ioctl support
- scsi: cxlflash: Refactor AFU capability checking
- scsi: cxlflash: Support LUN provisioning
- scsi: cxlflash: Support AFU debug
- scsi: cxlflash: Support WS16 unmap
- scsi: cxlflash: Remove zeroing of private command data
- scsi: cxlflash: Update TMF command processing
- scsi: cxlflash: Avoid double free of character device
- scsi: cxlflash: Update send_tmf() parameters
- scsi: cxlflash: Update debug prints in reset handlers

  * Ath10k to read different board data file if specify in SMBIOS (LP: #1666742)
- ath10k: search SMBIOS for OEM board file extension

  * APST gets enabled against explicit kernel option (LP: #1699004)
- nvme: Display raw APST configuration via DYNAMIC_DEBUG
- nvme: Add nvme_core.force_apst to ignore the NO_APST quirk
- nvme: explicitly disable APST on quirked devices

  * Quirk for non-compliant PCI bridge on HiSilicon D05 board (LP: #1698706)
- SAUCE: PCI: Support hibmc VGA cards behind a misbehaving HiSilicon bridge

  * New NVLINK2 patches (LP: #1701272)
- powerpc/powernv/npu-dma: Add explicit flush when sending an ATSD
- powerpc/npu-dma: Remove spurious WARN_ON when a PCI device has no of_node

  * ERAT invalidate on context switch removal (LP: #1700819)
- powerpc: Only do ERAT invalidate on radix context

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-08-01 Thread dann frazier 
** Attachment added: "console.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+attachment/4925349/+files/console.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-08-01 Thread dann frazier 
Attached is a boot log w/ the fixed kernel that shows the SMMU being
discovered, the system successfully mounting the root disk, etc.
However, the system does seem to hang at the end with the networking
failing to come up.

This is an improvement, and booting in non-ACPI mode shows no
regressions, so I'll mark this as verified. However, it does look like
there is more needed to get to a fully functional system in ACPI-mode.

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-07-21 Thread Kleber Sacilotto de Souza 
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-07-14 Thread Thadeu Lima de Souza Cascardo 
** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-07-13 Thread Seth Forshee 
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1703437] Re: New ACPI identifiers for ThunderX SMMU

2017-07-10 Thread dann frazier 
This is fixed by the following commit in linux-next:

commit 84c24379a783c514e5ff7c8fc8a21cf8d64fd05f
Author: Robin Murphy 
Date:   Mon Jun 19 16:41:56 2017 +0100

iommu/arm-smmu: Plumb in new ACPI identifiers

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1703437

Title:
  New ACPI identifiers for ThunderX SMMU

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  [Impact]
  With current firmware (e.g. AMI 018 for CRBs), Cavium ThunderX-based nodes in 
ACPI mode fail to boot due to an undetected SMMU device. This doesn't impact 
the currently certified Cavium ThunderX-based systems, which boot in non-ACPI 
mode by default. However, future ThunderX-based platforms will likely use ACPI 
by default, and they would suffer from this bug.

  [Test Case]
  Boot a Cavium CRB w/ 018 firmware. Note that lack of SMMU boot messages, and 
the failure to boot due to undetected devies (specifically, no root disk found).

  [Regression Risk]
  The upstream fix is adding support for new device IDs, which were previously 
unsupported and would've previously failed to probe w/ -ENODEV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp