lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50CB9FF8.2070502@redhat.com>
Date:	Fri, 14 Dec 2012 16:54:00 -0500
From:	Don Dutile <ddutile@...hat.com>
To:	Jason Gao <pkill.2012@...il.com>
CC:	Alex Williamson <alex.williamson@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-pci@...r.kernel.org, kvm <kvm@...r.kernel.org>
Subject: Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is
 not set] Vt-d & intel_iommu

On 12/13/2012 09:01 PM, Jason Gao wrote:
> On Fri, Dec 14, 2012 at 12:23 AM, Alex Williamson
> <alex.williamson@...hat.com>  wrote:
>>
>> Device 03:00.0 is your raid controller:
>>
>> 03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078 (rev 04)
>>
>> For some reason it's trying to read from ffe65000, ffe8a000, ffe89000,
>> ffe86000, ffe87000, ffe84000.  Those are in reserved memory regions, so
>> it's not reading an OS allocated buffer, which probably means it's some
>> kind of side-band communication with a management controller.  I'd guess
>> it's a BIOS bug and there should be an RMRR covering those accesses.
>> Thanks,
>
> First of all ,I want to known whether I can ignore these errors on the
> production server,and do these error may affect the system?
>
> By the way,when I removed the "intel_iommu=on" from /etc/grub.conf,no
> DMAR related errors occur
>
well, if you don't enable the IOMMU, then it won't have IOMMU faults! ;-)

> It's a strange thing,other three Dell R710 servers with the same bios
> version v. 6.3.0, same kernel 2.6.32-279.14.1 on RHEL6u3(Centos 6u3)
> ,but these errors don't appear on these tree servers
>
mptsas or smi fw has to be different....

> Anyone have any idea for this ?
>
> thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ