linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Coatti <fabio.coatti@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: iwlwifi problem with iommu/intel-iommu: Enable CONFIG_DMA_DIRECT_OPS=y and clean up intel_{alloc,free}_coherent()
Date: Mon, 02 Jul 2018 20:23:00 +0200	[thread overview]
Message-ID: <2006717.WYUGMmW7i0@hobbes> (raw)
In-Reply-To: <20180702131951.GA5786@lst.de>

On Monday 2 July 2018 15:19:51 CEST Christoph Hellwig wrote:
> > By reverting this commit the card works again, tested in 4.17.3 . I've
> > noticed that the corresponding amd commit (
> > b468620f2a1dfdcfddfd6fa54367b8bcc1b51248) has been reverted in linus tree
> > (e16c4790de39dc861b749674c2a9319507f6f64f), and 4.16.X stable tree iirc, 
> > but the intel one has not been reverted.
> > 
> > hw: Lenovo P50 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
> > 
> > Please let me know if more details are needed, but CC: me as I'm not
> > currently subscribed to LKML.
> 
> It probablty is the same issue.  Did you check if you can just revert
> the commit cleanly on top of current mainline and that fixes the issue
> for you?

Yep, it does. I issued a 
git revert d657c5c73ca987214a6f9436e435b34fc60f332a
on mainline (4.18-rc3) and recompiled, the card works just fine.



  reply	other threads:[~2018-07-02 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 15:42 iwlwifi problem with iommu/intel-iommu: Enable CONFIG_DMA_DIRECT_OPS=y and clean up intel_{alloc,free}_coherent() Fabio Coatti
2018-07-02 13:19 ` Christoph Hellwig
2018-07-02 18:23   ` Fabio Coatti [this message]
2018-07-05 19:32     ` Christoph Hellwig
     [not found]       ` <CADpTngUNvFZefnoMHJUhWT0LL_OXHpSzgYF+XxKbceRvKhFSjQ@mail.gmail.com>
2018-07-23 12:38         ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2006717.WYUGMmW7i0@hobbes \
    --to=fabio.coatti@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).