* Current git fails to boot with VT-D enabled due to flood of DMAR errors
@ 2009-09-20 4:32 Robert Hancock
2009-09-20 4:41 ` David Woodhouse
0 siblings, 1 reply; 4+ messages in thread
From: Robert Hancock @ 2009-09-20 4:32 UTC (permalink / raw)
To: linux-kernel; +Cc: David Woodhouse
On an Asus P7P55D Pro-based system (Lynnfield CPU), with Intel VT-d
enabled in the BIOS, on 2.6.30.5 (the previous version I tested) I get
these lines in dmesg:
DMAR:Host address width 36
DMAR:DRHD (flags: 0x00000001)base: 0x00000000fed90000
DMAR:RMRR base: 0x00000000000e4000 end: 0x00000000000e7fff
DMAR:RMRR base: 0x00000000bf7ec000 end: 0x00000000bf7fffff
Not all IO-APIC's listed under remapping hardware
In current -git, I get these lines as well, but then I get this:
DRHD: handling fault status reg ffffffff
DMAR:[DMA Read] Request device [ff:1f.7] fault addr fffffffffffff000
DMAR:[fault reason 255] Unknown
The last two lines repeat in a continuous flood and the system doesn't
boot. This happens even if I pass "intel_iommu=off" (which seems like
it's already the default).
Could be a kernel bug or a BIOS bug, but in the latter case we should
probably deal with it better. The registers all reading FF seems like
maybe the registers are disabled or something..
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Current git fails to boot with VT-D enabled due to flood of DMAR errors
2009-09-20 4:32 Current git fails to boot with VT-D enabled due to flood of DMAR errors Robert Hancock
@ 2009-09-20 4:41 ` David Woodhouse
2009-09-20 4:46 ` Robert Hancock
0 siblings, 1 reply; 4+ messages in thread
From: David Woodhouse @ 2009-09-20 4:41 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
On Sat, 2009-09-19 at 22:32 -0600, Robert Hancock wrote:
> On an Asus P7P55D Pro-based system (Lynnfield CPU), with Intel VT-d
> enabled in the BIOS, on 2.6.30.5 (the previous version I tested) I get
> these lines in dmesg:
>
> DMAR:Host address width 36
> DMAR:DRHD (flags: 0x00000001)base: 0x00000000fed90000
> DMAR:RMRR base: 0x00000000000e4000 end: 0x00000000000e7fff
> DMAR:RMRR base: 0x00000000bf7ec000 end: 0x00000000bf7fffff
> Not all IO-APIC's listed under remapping hardware
>
> In current -git, I get these lines as well, but then I get this:
>
> DRHD: handling fault status reg ffffffff
> DMAR:[DMA Read] Request device [ff:1f.7] fault addr fffffffffffff000
> DMAR:[fault reason 255] Unknown
>
> The last two lines repeat in a continuous flood and the system doesn't
> boot. This happens even if I pass "intel_iommu=off" (which seems like
> it's already the default).
>
> Could be a kernel bug or a BIOS bug, but in the latter case we should
> probably deal with it better. The registers all reading FF seems like
> maybe the registers are disabled or something..
This ought to be 'fixed' in linux-next by this commit:
http://git.infradead.org/iommu-2.6.git/commitdiff/0815565ad
Please try linux-next or the iommu tree from
git://git.infradead.org/iommu-2.6.git
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Current git fails to boot with VT-D enabled due to flood of DMAR errors
2009-09-20 4:41 ` David Woodhouse
@ 2009-09-20 4:46 ` Robert Hancock
2009-09-20 5:09 ` David Woodhouse
0 siblings, 1 reply; 4+ messages in thread
From: Robert Hancock @ 2009-09-20 4:46 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-kernel
On 09/19/2009 10:41 PM, David Woodhouse wrote:
> On Sat, 2009-09-19 at 22:32 -0600, Robert Hancock wrote:
>> On an Asus P7P55D Pro-based system (Lynnfield CPU), with Intel VT-d
>> enabled in the BIOS, on 2.6.30.5 (the previous version I tested) I get
>> these lines in dmesg:
>>
>> DMAR:Host address width 36
>> DMAR:DRHD (flags: 0x00000001)base: 0x00000000fed90000
>> DMAR:RMRR base: 0x00000000000e4000 end: 0x00000000000e7fff
>> DMAR:RMRR base: 0x00000000bf7ec000 end: 0x00000000bf7fffff
>> Not all IO-APIC's listed under remapping hardware
>>
>> In current -git, I get these lines as well, but then I get this:
>>
>> DRHD: handling fault status reg ffffffff
>> DMAR:[DMA Read] Request device [ff:1f.7] fault addr fffffffffffff000
>> DMAR:[fault reason 255] Unknown
>>
>> The last two lines repeat in a continuous flood and the system doesn't
>> boot. This happens even if I pass "intel_iommu=off" (which seems like
>> it's already the default).
>>
>> Could be a kernel bug or a BIOS bug, but in the latter case we should
>> probably deal with it better. The registers all reading FF seems like
>> maybe the registers are disabled or something..
>
> This ought to be 'fixed' in linux-next by this commit:
> http://git.infradead.org/iommu-2.6.git/commitdiff/0815565ad
>
> Please try linux-next or the iommu tree from
> git://git.infradead.org/iommu-2.6.git
Yeah, I just came across that patch. Is that going to get pushed for
2.6.32? It seems like something caused us to start tripping over this by
default when we didn't before. (Passing intel_iommu=on with 2.6.30.5
does cause the same problem.)
I'll try and report the problem to Asus, obviously something's borked
with VT-d in their BIOS currently..
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Current git fails to boot with VT-D enabled due to flood of DMAR errors
2009-09-20 4:46 ` Robert Hancock
@ 2009-09-20 5:09 ` David Woodhouse
0 siblings, 0 replies; 4+ messages in thread
From: David Woodhouse @ 2009-09-20 5:09 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-kernel
On Sat, 2009-09-19 at 22:46 -0600, Robert Hancock wrote:
>
> Yeah, I just came across that patch. Is that going to get pushed for
> 2.6.32? It seems like something caused us to start tripping over this
> by default when we didn't before. (Passing intel_iommu=on with
> 2.6.30.5 does cause the same problem.)
Yes, I'll push it in the next day or so. Just waiting for another
last-minute fix to be tested by someone other than me, and then I'll ask
Linus to pull.
> I'll try and report the problem to Asus, obviously something's borked
> with VT-d in their BIOS currently..
Good luck with that. Their normal response is to say "it boots Windows
so it must be perfect". Despite the fact that Windows doesn't actually
use VT-d. Idiots.
--
dwmw2
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-09-20 5:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-09-20 4:32 Current git fails to boot with VT-D enabled due to flood of DMAR errors Robert Hancock
2009-09-20 4:41 ` David Woodhouse
2009-09-20 4:46 ` Robert Hancock
2009-09-20 5:09 ` David Woodhouse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®