From: Marius Vlad <marius.c.vlad@intel.com>
To: Adam Morrison <mad@cs.technion.ac.il>
Cc: Omer Peleg <omer@cs.technion.ac.il>,
David.Woodhouse@intel.com, intel-gfx@lists.freedesktop.org,
iommu@lists.linux-foundation.org
Subject: Re: iommu/vt-d: Use per-cpu IOVA caching, suspend-to-ram causes machine hang
Date: Mon, 6 Jun 2016 13:32:10 +0300 [thread overview]
Message-ID: <20160606103209.GA30777@mcvlad-wk.rb.intel.com> (raw)
In-Reply-To: <CAHMfzJkuRBCMtkGniODGxfrZrmthx9nHog8vq-jCTMVJb_64Bw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 563 bytes --]
Yes, that does it. Thanks.
On Mon, Jun 06, 2016 at 12:02:30AM +0300, Adam Morrison wrote:
> > Hi Omer the following commit introduced a regression when doing
> > suspend-to-ram. The machine never wakes up. We have more than
> > a few machines that hang: SNB-i7-2620m, IVB-3370, HSW-4470r, BDW-5600u,
> > BDW-525u.
>
> Jan Niehusmann posted a patch that fixes a similar problem:
>
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1158159.html
>
> Can you please try it and see if it does the trick for you?
>
> Thanks,
> Adam
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-06 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 21:02 iommu/vt-d: Use per-cpu IOVA caching, suspend-to-ram causes machine hang Adam Morrison
2016-06-06 10:32 ` Marius Vlad [this message]
2016-06-06 12:20 ` [PATCH v2] iommu/vt-d: fix overflow of iommu->domains array Jan Niehusmann
2016-06-27 11:23 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2016-06-05 18:13 iommu/vt-d: Use per-cpu IOVA caching, suspend-to-ram causes machine hang Marius Vlad
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=20160606103209.GA30777@mcvlad-wk.rb.intel.com \
--to=marius.c.vlad@intel.com \
--cc=David.Woodhouse@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=mad@cs.technion.ac.il \
--cc=omer@cs.technion.ac.il \
/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).