search for: iohe

All, just having spotted the backport of Linux commit 03bbcb2e I notice a certain discrepancy with the Xen commit having the same purpose as well as with the actual specification updates: The Linux solution keys off of device IDs 3403 and 3406, as listed in the specification update, but this way fails to cover the X58 chipset, which has - under different numbers (62 and 69) - the same errata

http://www.intel.com/content/www/us/en/chipsets/5520-and-5500-chipset-ioh-specification-update.html Stepping B-3 has two errata (#47 and #53) related to Interrupt remapping, to which the workaround is for the BIOS to completely disable interrupt remapping. These errata are fixed in stepping C-2. Unfortunately this chipset is very common and many BIOSes are not disabling remapping. We can

My setup: A SuperMicro 24-drive chassis with Intel dual-processor motherboard, three LSI SAS3081E controllers, and 24 SATA 2TB hard drives, divided into three pools with each pool a single eight-disk RAID-Z2. (Boot is an SSD connected to motherboard SATA.) This morning I got a cheerful email from my monitoring script: "Zchecker has discovered a problem on bigdawg." The full output is

Hi, I am working with a westemere based server. I need to find out if the NIC installed there supports SR-IOV - what would be the best way to determine that? Regards, Kashyap hwconfig ------------- Summary: HP DL160 G6, 2 x Xeon E5620 2.40GHz, 15.7GB / 16GB 1333MHz, 1 x 500GB SATA System: HP ProLiant DL160 G6, C-2N/16/500, ySPEC 25.0 Processors: 2 x Xeon E5620 2.40GHz (HT

2.2.6 installed from rpm on rh 7.2 system... I'm trying to use pam_winbind and apache's basic authentication to restrict access to certain directories served by apache. It does work, but when I enter a wrong password I get this error in log.winbindd: Plain-text authentication for user jarboed returned NT_STATUS_WRONG_PASSWORD Is there a way that pam_winbind.so can encrypt the passwords

1: IOMMU: properly check whether interrupt remapping is enabled 2: AMD IOMMU: only disable when certain IVRS consistency checks fail 3: VT-d: deal with 5500/5520/X58 errata Patch 1 and 2 are version 2 of a previously submitted, then withdrawn patch following up after XSA-36. Patch 3 is version 3 of a patch previously sent by Malcolm and Andrew. Signed-off-by: Jan Beulich

You could always use 40-gigabit between the two storage systems which would speed things dramatically, or back to back 56-gigabit IB. ---------------------------------------- From: zfs-discuss-request@opensolaris.org Sent: Monday, March 18, 2013 11:01 PM To: zfs-discuss@opensolaris.org Subject: zfs-discuss Digest, Vol 89, Issue 12 Send zfs-discuss mailing list submissions to

On Windows, there exist at least two APIs for dealing with the Registry: The Win32 API (RegCreateKeyA, RegCreateKeyW, etc.) works with null-terminated ASCII or UTF-16 strings. The native API (ZwCreateKey, etc.), on the other hand works with UTF-16 strings that are stored as buffers+length and may contain null characters. Malware authors have been relying on the Win32 API's inability to

--- images/README | 15 +++++++++++++++ images/mkzero/Makefile | 7 +++++++ images/mkzero/mkzero.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ images/special | Bin 0 -> 8192 bytes 4 files changed, 70 insertions(+) create mode 100644 images/mkzero/Makefile create mode 100644 images/mkzero/mkzero.c create mode 100644 images/special diff --git a/images/README

On 2014/7/4 10:45, Brian Becker wrote: > Yijing, > > cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting > that it supports MSI. However, this "00:0e.0 PCI bridge: PLX > Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" > is a component of the addin card. Wouldn't the lack of support for MSI > by the chipset "00:00.0

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- hw/9pfs/virtio-9p-device.c | 43 ++++++---- hw/ac97.c | 39 +++++---- hw/acpi_piix4.c | 59 +++++++------ hw/apb_pci.c | 54 ++++++++----- hw/bonito.c | 30 ++++--- hw/cirrus_vga.c | 33 +++++--- hw/dec_pci.c | 57 ++++++++----- hw/e1000.c

Yijing, cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting that it supports MSI. However, this "00:0e.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" is a component of the addin card. Wouldn't the lack of support for MSI by the chipset "00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 01)"

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

Hi, I''m trying to get VGA passthrough to work to an XP x64 guest, and I''m seeing "interesting" things happening. I''m using the kernel and userspace tools from here: http://xen.crc.id.au/support/guides/install/# on Scientific Linux 6. I gave up on trying to get an Nvidia card to work in the guest having read about the extra patches required to get a

Signed-off-by: Scott Seago <sseago at redhat.com> --- AUTHORS | 17 ++++++ README | 10 +++ conf/ovirt-agent | 12 ++++ conf/ovirt-db-omatic | 12 ++++ conf/ovirt-host-browser | 12 ++++