Re: SR-IOV problem with Intel 82599EB (not enough MMIO resources for SR-IOV)
I'm very sorry for delayed reply.now SR-IOV works for me in Centos 6.3,thank all of you. On Fri, Nov 9, 2012 at 11:26 PM, Bjorn Helgaas wrote: > Linux normally uses the resource assignments done by the BIOS, but it > is possible for the kernel to reassign those. We don't have good > automatic support for that yet, but on a recent upstream kernel, you > can try "pci=realloc". I doubt this option is in CentOS 6.3, though Thank you very much,I try "pci=realloc" in Centos 6.3,and now it works for me. On Sat, Nov 10, 2012 at 2:08 AM, Li, Sibai wrote: > DellR710 with the latest BIOS should work fine for SR-IOV. My BIOS is v.6.3.0 > and release date is 07/24/2012 > Please check if you configured intel_iommu=on in the grub.conf file. > If you did, check your kernel .config file under Device Drivers-> IOMMU > Hardware support->enable Support for Intel IOMMU using DMA remapping Devices, > enable Intel DMA Remapping Devices by Default, enable Support for Interrupt > Remapping. thank you Sibai,Our server "Dell R710",its BIOS version is just v.6.3.0 and release date is 07/24/2012,and I also configured intel_iommu=on in the grub.conf file,but I can't find these IOMMU options in "Device Drivers" in my kernel(2.6.32-279) .config file , btw my os is Centos 6.3(RHEL6.3),although the problem solved,I'd like to know what's your os version ,kernel version? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: SR-IOV problem with Intel 82599EB (not enough MMIO resources for SR-IOV)
> The BIOS in your machine doesn't support SR-IOV. You'll need to ask the > manufacturer for a BIOS upgrade, if in fact one is available. Sometimes > they're not. very thanks Greg,my server Dell R710 with latest BIOS version and option for SR-IOV(SR-IOV Global Enable->Enabled) opened,I'm confused that Does R710 provide full support for SR-IOV, kernel or ixgbe driver's bug? but I'm not sure where the problem lies,anyone has any experience about this? . -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
Dear List: Description of problem: After installed Centos 6.3(RHEL6.3) on my Dell R710(lastest bios:Version: 6.3.0,Release Date: 07/24/2012) server,and updated lastest kernel "2.6.32-279.14.1.el6.x86_64",I want to use the Intel 82576 ET Dual Port nic's SR-IOV feature,assigning VFs to kvm guest appended kernel boot parameter: intel_iommu=on,after boot with the following messages: Dec 13 16:58:15 2 kernel: DRHD: handling fault status reg 2 Dec 13 16:58:15 2 kernel: DMAR:[DMA Read] Request device [03:00.0] fault addr ffe65000 Dec 13 16:58:15 2 kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 13 16:58:15 2 kernel: DRHD: handling fault status reg 102 Dec 13 16:58:15 2 kernel: DMAR:[DMA Read] Request device [03:00.0] fault addr ffe8a000 Dec 13 16:58:15 2 kernel: DMAR:[fault reason 06] PTE Read access is not set Dec 13 16:58:15 2 kernel: scsi 0:0:32:0: Enclosure DP BACKPLANE1.07 PQ: 0 ANSI: 5 Dec 13 16:58:15 2 kernel: DRHD: handling fault status reg 202 Dec 13 16:58:15 2 kernel: DMAR:[DMA Read] Request device [03:00.0] fault addr ffe89000 Dec 13 16:58:15 2 kernel: DMAR:[fault reason 06] PTE Read access is not set full dmesg detail: http://pastebin.com/BzFQV0jU lspci -vvv full detail: http://pastebin.com/9rP2d1br it's a production server,and I'm not sure if this is a critical problem,how to fix it,any help would be greatly appreciated. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
On Fri, Dec 14, 2012 at 12:23 AM, Alex Williamson 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 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 Anyone have any idea for this ? thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
On Fri, Dec 14, 2012 at 12:45 PM, Alex Williamson wrote: > Is the MegaRAID firmware and system management firmware the same as > well? Thanks. I'v updated all the firmware using Dell's firmware-tools: # inventory_firmware Wait while we inventory system: System inventory: BIOS = 6.3.0 SAS/SATA Backplane 0:0 Backplane Firmware = 1.07 PERC 6/i Integrated Controller 0 Firmware = 6.3.1-0003 Dell OS Drivers Pack, v.6.5.3, A00 = 6.5.3 Dell Lifecycle Controller = 1.5.5.27 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth1) = 7.2.20 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth0) = 7.2.20 ST3600057SS Firmware = es66 iDRAC6 = 1.92 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth2) = 7.2.20 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth3) = 7.2.20 Dell 32 Bit Diagnostics, v.5154A0, 5154.1 = 5154a0 System BIOS for PowerEdge R710 = 6.3.0 Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
On Fri, Dec 14, 2012 at 2:56 PM, Jason Gao wrote:
> On Fri, Dec 14, 2012 at 12:45 PM, Alex Williamson
> wrote:
>> Is the MegaRAID firmware and system management firmware the same as
>> well? Thanks.
>
> I'v updated all the firmware using Dell's firmware-tools:
>
> # inventory_firmware
> Wait while we inventory system:
> System inventory:
> BIOS = 6.3.0
> SAS/SATA Backplane 0:0 Backplane Firmware = 1.07
> PERC 6/i Integrated Controller 0 Firmware = 6.3.1-0003
> Dell OS Drivers Pack, v.6.5.3, A00 = 6.5.3
> Dell Lifecycle Controller = 1.5.5.27
> NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth1) = 7.2.20
> NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth0) = 7.2.20
> ST3600057SS Firmware = es66
> iDRAC6 = 1.92
> NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth2) = 7.2.20
> NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth3) = 7.2.20
> Dell 32 Bit Diagnostics, v.5154A0, 5154.1 = 5154a0
> System BIOS for PowerEdge R710 = 6.3.0
>
> Thanks
#lspci - -s 03:00.0|grep fail:
pcilib: sysfs_read_vpd: read failed: Connection timed out
#strace lspci - -s 03:00.0|grep fail:
open("/sys/bus/pci/devices/:03:00.0/vpd", O_RDONLY) = 4
pread(4, 0x7fff30670b3f, 1, 0) = -1 ETIMEDOUT (Connection timed out)
write(2, "pcilib: ", 8pcilib: ) = 8
write(2, "sysfs_read_vpd: read failed: Con"..., 49sysfs_read_vpd: read
failed: Connection timed out) = 49
write(2, "\n", 1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
On Sat, Dec 15, 2012 at 5:54 AM, Don Dutile wrote: > mptsas or smi fw has to be different this server: # inventory_firmware Wait while we inventory system: System inventory: BIOS = 6.3.0 SAS/SATA Backplane 0:0 Backplane Firmware = 1.07 PERC 6/i Integrated Controller 0 Firmware = 6.3.1-0003 Dell OS Drivers Pack, v.6.5.3, A00 = 6.5.3 Dell Lifecycle Controller = 1.5.5.27 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth1) = 7.2.20 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth0) = 7.2.20 ST3600057SS Firmware = es66 iDRAC6 = 1.92 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth2) = 7.2.20 NetXtreme II BCM5709 Gigabit Ethernet rev 20 (eth3) = 7.2.20 Dell 32 Bit Diagnostics, v.5154A0, 5154.1 = 5154a0 System BIOS for PowerEdge R710 = 6.3.0 other servers: # inventory_firmware Wait while we inventory system: System inventory: BIOS = 6.3.0 SAS/SATA Backplane 0:0 Backplane Firmware = 1.07 PERC H700 Integrated Controller 0 Firmware = 12.10.4-0001 Dell OS Drivers Pack, 7.1.0.9, A00 = 7.1.0.9 Dell Lifecycle Controller, 1.5.5.27, A00 = 1.5.5.27 ST3600057SS Firmware = es65 iDRAC6 = 1.90 Dell 32 Bit Diagnostics, v.5154A0, 5154. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: DMAR and DRHD errors[DMAR:[fault reason 06] PTE Read access is not set] Vt-d & intel_iommu
On Sat, Dec 15, 2012 at 5:55 AM, Don Dutile wrote: > forgot: did you check that all the bios settings are the same btwn > the 710 systems? Bios settings should be the same between servers, I'v ignored these errors and run KVM on this server,deployed non-critical java production applications running on kvm guest, thanks -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
