From: Weidong Han <weidong.han@intel.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Xen 4.0.0-rc7 problem/hang with vt-d DMAR parsing
Date: Wed, 24 Mar 2010 08:40:16 +0800 [thread overview]
Message-ID: <4BA95F70.8080904@intel.com> (raw)
In-Reply-To: <20100323200515.GZ1878@reaktio.net>
Pasi Kärkkäinen wrote:
> On Tue, Mar 23, 2010 at 07:54:33PM +0000, Keir Fraser wrote:
>
>> On 23/03/2010 19:37, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
>>
>>
>>>> It's not impossible that the BIOS VT-d support is just broken (I assume
>>>> you've never tested VT-d on this particular type of system before).
>>>>
>>> Yeah, I've never used VT-d on this system earlier, so it could just be broken
>>> BIOS.
>>> I guess Xen still shouldn't hang on it?
>>>
>> We'd prefer to gracefully disable VT-d.
>>
>>
>
> 4.0.0-rc7 (without any extra cmdline options) does disable vt-d and boot ok,
> after 'hanging' for 30 seconds while parsing the DMAR tables.
>
> If I add "iommu=verbose" option for Xen, then it'll print huge amount of stuff
> like I pasted earlier.. and it takes forever to print all that.
>
The BIOS is likely broken. Could you dump the ACPI tables? Then we can
confirm if it's BIOS issue. Maybe we can cook a patch to detect this
issue (dmaru->address == 0), and handle it more gracefully. I will have
a look at it.
Regards,
Weidong.
> Hmm.. wondering if the patch Jan just sent will help with that.
> Sounds like it might help :)
>
> -- Pasi
>
>
next prev parent reply other threads:[~2010-03-24 0:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 14:27 Xen 4.0.0-rc7 problem/hang with vt-d DMAR parsing Pasi Kärkkäinen
2010-03-23 14:40 ` Jan Beulich
2010-03-23 14:40 ` Pasi Kärkkäinen
2010-03-23 14:48 ` Keir Fraser
2010-03-23 19:37 ` Pasi Kärkkäinen
2010-03-23 19:54 ` Keir Fraser
2010-03-23 20:05 ` Pasi Kärkkäinen
2010-03-24 0:40 ` Weidong Han [this message]
2010-03-24 1:52 ` Cui, Dexuan
2010-03-24 8:24 ` Jan Beulich
2010-03-24 8:54 ` Cui, Dexuan
2010-03-24 9:02 ` Weidong Han
2010-03-24 9:10 ` Pasi Kärkkäinen
2010-03-24 9:46 ` Jan Beulich
2010-03-24 11:00 ` Weidong Han
2010-03-24 11:11 ` Jan Beulich
2010-03-25 0:55 ` Weidong Han
2010-03-25 8:43 ` Jan Beulich
2010-03-25 9:05 ` Weidong Han
2010-03-25 9:16 ` Jan Beulich
2010-03-25 9:21 ` Weidong Han
2010-03-25 9:30 ` Jan Beulich
2010-03-25 9:34 ` Pasi Kärkkäinen
2010-03-25 9:44 ` Keir Fraser
2010-03-26 19:20 ` Pasi Kärkkäinen
2010-03-29 6:42 ` Cui, Dexuan
2010-03-24 17:34 ` Nadolski, Ed
2010-03-25 0:04 ` Weidong Han
2010-04-05 18:00 ` Nadolski, Ed
2010-04-07 1:43 ` Weidong Han
2010-03-24 8:50 ` Pasi Kärkkäinen
2010-03-26 19:45 ` Pasi Kärkkäinen
2010-03-29 6:48 ` Cui, Dexuan
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=4BA95F70.8080904@intel.com \
--to=weidong.han@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/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).