kernel-packages team mailing list archive

[Samir Methia <1386490@xxxxxxxxxxxxxxxxxx>]

** Also affects: lomond
   Importance: Undecided
       Status: New

** Tags added: mcdivitt-fwd-comp

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

Title:
  HP ProLiant m400 nic doesn't work after trusty

Status in The Lomond project:
  New
Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Utopic:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in debian-installer source package in Vivid:
  Confirmed
Status in linux source package in Vivid:
  Confirmed

Bug description:
  Starting in 3.15, arm64 began defaulting to non-coherent dma_ops:

  commit c7a4a7658d689f664050c45493d79adf053f226e
  Author: Ritesh Harjani <ritesh.harjani@xxxxxxxxx>
  Date:   Wed Apr 23 06:29:46 2014 +0100

      arm64: Make default dma_ops to be noncoherent

  Firmware (dtb in the case of the m400) is responsible for telling the
  kernel when a device requires coherent dma_ops. However, as of utopic,
  this property is not being inherited by downstream devices.
  Specifically, the xgene-pcie device is marked as coherent, but the
  devices behind it (mellanox card) still get initialized with non-
  coherent ops.

  This results in the mlx4 driver bailing out with the following messages:
  [   18.703635] mlx4_core 0000:01:00.0: command 0x23 timed out (go bit not cleared)
  [   18.710911] mlx4_core 0000:01:00.0: Failed to initialize queue pair table, aborting

  
  There's an upstream discussion on the topic here:
    http://www.spinics.net/lists/arm-kernel/msg362320.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/lomond/+bug/1386490/+subscriptions