Hi Raj, Lu, thanks for the fast feedback :)
On 9/28/17 20:00, Raj, Ashok wrote:
has it worked ever with intel_iommu=on?
Good point. I just tested that by rolling back to 4.12.13-1
and manually activating `intel_iommu=on`. As expected, no,
resume is similarly broken.
`intel_iommu={on, igfx_on}` probably have been breaking resume
for a long time on my system, I just happened to notice it now
due to being `on` by default.
On 9/29/17 00:29, Lu Baolu wrote:
> I will look into it. But we will have a holiday till Oct. 8.
> We probably won't see any progress before I am back.
Awesome! Note I will also be away mid-October, so if you
ask for feedback at this moment it might be a while before
I answer. But be sure I will.
Also, not sure if this is related or a separate bug, but looking at
my system logs I see two errors logged when `intel_iommu` is `on`:
DMAR: DRHD: handling fault status reg 3
DMAR: [DMA Read] Request device [00:12.4] fault addr b7fff000
[fault reason 02] Present bit in context entry is clear
Feel free to ask for more info about that DMAR error, or ignore
it if you know it's irrelevant / already tracked elsewhere :)
Amending https://bugzilla.kernel.org/show_bug.cgi?id=197029 with
the new information.
Thanks again, good day everyone.
_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu
