← Back to team overview

kernel-packages team mailing list archive

[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu


Did you happen to have a chance to test the latest mainline kernel,
posted in comment #2?  Mainline is now up to -rc7, so the link to the
kernel would be:


If the bug is fixed in mainline, we can perform a reverse bisect to
identify the commit that fixes it.

However, if the bug still exists in mainline, we would want to perform a
regular kernel bisect to find the commit that introduced the regression.
To perform a bisect, we need to identify the last good and first bad
kernel versions.  Per comment #7 v3.16 is good, but v3.19 is bad.  We
would want to test the versions in between.  So if mainline still has
the bug, can you test the following upstream kernels:

v3.17: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/
v3.18: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-vivid/

Once we have these results, we can narrow down the versions further to
individual release candidates.

Thanks in advance!

** Tags added: performing-bisect

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

To manage notifications about this bug go to: