From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Dheeraj CVR <cvr.dheeraj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [BUGREPORT] Intel X58 Boards don't boot after "iommu/vt-d: Make root entry visible for hardware right after allocation"
Date: Wed, 15 Jun 2016 18:11:49 +0200 [thread overview]
Message-ID: <20160615161149.GJ13971@8bytes.org> (raw)
In-Reply-To: <CAH-=PyTaR-xH7D4eOnFkB-7gojdZW08yHEPP2Gw2-0GjWTA4dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Apr 29, 2016 at 04:41:23PM +0400, Dheeraj CVR wrote:
> Hi Joerg,
>
> Did you find time to have a look at the dmesg that I have sent to you in the
> earlier email? Please let me know if you need any more debugging info to
> diagnose this issue.
Yes, I had a look at the dmesg and went through the code again. I have
no clue yet why that commit causes the issue on your machine. Between
the two places in the code where the set_root_entry calls are/were,
there are no other things going on with the iommu hardware, so it
shouldn't matter when setting the root entry happens earlier.
Can you try to track down (with some debug code) exactly where it is
hanging? That might bring some more light into the issue.
Joerg
next prev parent reply other threads:[~2016-06-15 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 20:35 [BUGREPORT] Intel X58 Boards don't boot after "iommu/vt-d: Make root entry visible for hardware right after allocation" Dheeraj CVR
[not found] ` <CAH-=PyRpjuKf0XJNyzkVLpggaaYq163AfA84SZ5=DQH2Ys5Lkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-25 3:19 ` Dheeraj CVR
[not found] ` <CAH-=PyR-6sY1vuzQSfJyh35Q+WqZKD70Ev7vDns+02h8j=m18Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-25 11:01 ` Joerg Roedel
[not found] ` <20160425110151.GE17926-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-04-25 11:31 ` Dheeraj CVR
[not found] ` <CAH-=PyTGF76sq7LvQH0-28DoK1dXGUOdnCF6z9shF_CWosWYwQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-29 12:41 ` Dheeraj CVR
[not found] ` <CAH-=PyTaR-xH7D4eOnFkB-7gojdZW08yHEPP2Gw2-0GjWTA4dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-15 16:11 ` Joerg Roedel [this message]
[not found] ` <20160615161149.GJ13971-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-06-16 6:26 ` Dheeraj CVR
[not found] ` <CAH-=PyRBZU95f0XPLZQXyaKLPx+K5iNsQs3ucQRj6BPfj9ERBA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-16 10:29 ` Joerg Roedel
[not found] ` <20160616102914.GA11432-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-06-16 16:11 ` Dheeraj CVR
[not found] ` <CAH-=PyREixkSp59v_ErYK6rn0X8KLS29XxVCd9u51Yy6+r2tKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-06-17 9:01 ` Joerg Roedel
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=20160615161149.GJ13971@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=cvr.dheeraj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.