search for: disable_msi

Hoping someone else has seen this before. I have a few dozen Dell R610 systems with CentOS 5.2 that are using kernels from 5.3 and 5.4 (2.6.18-128.1.10.el5 & 2.6.18-164.6.1.el5), that at random lose layer 2 network connectivity either partially or totally. Running tcpdump on the interface reveals only ARP broadcasts, no responses. Switch reports no packets being received on the interface.

...pci:v000014E4d0000164Csv*sd*bc*sc*i* alias: pci:v000014E4d0000164Asv*sd*bc*sc*i* alias: pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i* alias: pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i* depends: vermagic: 2.6.16-2-xen-686 SMP 686 gcc-4.0 parm: disable_msi:Disable Message Signaled Interrupt (MSI) (int) from the debian xen kernel: Linux xen 2.6.16-2-xen-686 #1 SMP Sun Jul 16 01:42:25 UTC 2006 i686 GNU/Linux In a dell poweredge 1950 If I swap eth0 from the broadcom to a usb ethernet card using the rtl8150 driver, the bridging works immediately. I&...

...pci:v000014E4d0000164Csv*sd*bc*sc*i* alias: pci:v000014E4d0000164Asv*sd*bc*sc*i* alias: pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i* alias: pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i* depends: vermagic: 2.6.16-2-xen-686 SMP 686 gcc-4.0 parm: disable_msi:Disable Message Signaled Interrupt (MSI) (int) from the debian xen kernel: Linux xen 2.6.16-2-xen-686 #1 SMP Sun Jul 16 01:42:25 UTC 2006 i686 GNU/Linux In a dell poweredge 1950 If I swap eth0 from the broadcom to a usb ethernet card using the rtl8150 driver, the bridging works im...

Has anyone managed to get CentOS 6 x86_64 running on a server with a Broadcom NetXtremeII BCM5709 network adaptor? If so have you seen any issues with the network freezing? On booting everything works fine then the network will just stop - can't ping anything. If we manually restart the network service it will run again for a few seconds/minutes before hanging again. We have even installed the

...=3 Destination Host Unreachable From 172.12.34.112 icmp_seq=4 Destination Host Unreachable From 172.12.34.112 icmp_seq=5 Destination Host Unreachable I cannot even ping blades in the same enclosure. Yet in windows server 2008 after putting the same IP pinging the same IPs works. I tried: - the disable_msi=1 parameter of the bnx2 driver - a fresh install of CentOS 6.3 - a fresh install of RHEL 6.2 - a live CD of CentOS 5.5 - Clonezilla-ubuntu and systemrescuecd (kernel 3.2) live CDs - CentOS 6.3 with the kernel(-headers,-firmware,-devel) updated to the latest (RPMs were copied with a USB/iLO) - the...

...164Csv*sd*bc*sc*i* alias: pci:v000014E4d0000164Asv*sd*bc*sc*i* alias: pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i* alias: pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i* depends: intree: Y vermagic: 3.10.13 SMP mod_unload modversions parm: disable_msi:Disable Message Signaled Interrupt (MSI) (int) pktgen config: clone_skb 32 pkt_size 64 delay 0 pgset "count 0" pgset "delay 0" pgset "flows 256" pgset "flowlen 8" grep . /proc/sys/net/bridge/bridge-nf-* /proc/sys/net/bridge/bridge-nf-call-arptables:1 /pr...

Hello everybody, we have a strange behaviour since a BDC was rebooted. We have an infrastructure were one big Samba server is defined as a PDC, and a few others servers are defined as BDC. This infrastructure is deployed in a school, so we have the PDC and one BDC for each section of the school (college, elementary school ...). Most of the clients computers are Windows XP, and the servers

...ave incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me know if you have any > feedback. Thanks. > > VMware PVSCSI driver - v5. > > Changelog (v5-v4) > - use bool for pvscsi _disable_msi, _disable_msix, _use_msg > - fix for 16 byte CDBs, max_cmd_len should be initialized to 16. > - bump the driver version. > - add <pv-drivers at vmware.com> in the MAINTAINERS file. > - rebase to 2.6.32-rc1. > > Changelog (v4-v3) > - use size_t type for a loop iterator....

...ave incorporated the remaining > few outstanding comments while rebasing the patch for 32-rc1. > > Please consider this for the SCSI tree. Also let me know if you have any > feedback. Thanks. > > VMware PVSCSI driver - v5. > > Changelog (v5-v4) > - use bool for pvscsi _disable_msi, _disable_msix, _use_msg > - fix for 16 byte CDBs, max_cmd_len should be initialized to 16. > - bump the driver version. > - add <pv-drivers at vmware.com> in the MAINTAINERS file. > - rebase to 2.6.32-rc1. > > Changelog (v4-v3) > - use size_t type for a loop iterator....

...ing Sixth time's a charm :) VMware PVSCSI driver - v6. Changelog (v6-v5) - remove unneeded header file includes. - make pvscsi_dev as a static function. - IRQF_SHARED only for INT/X, pass zero for rest. - use __get_free_pages to allocate ctx->sgl. Changelog (v5-v4) - use bool for pvscsi _disable_msi, _disable_msix, _use_msg - fix for 16 byte CDBs, max_cmd_len should be initialized to 16. - bump the driver version. - add <pv-drivers at vmware.com> in the MAINTAINERS file. - rebase to 2.6.32-rc1. Changelog (v4-v3) - use size_t type for a loop iterator. - use IS_ALIGNED instead of ~PAGE_M...

...ing Sixth time's a charm :) VMware PVSCSI driver - v6. Changelog (v6-v5) - remove unneeded header file includes. - make pvscsi_dev as a static function. - IRQF_SHARED only for INT/X, pass zero for rest. - use __get_free_pages to allocate ctx->sgl. Changelog (v5-v4) - use bool for pvscsi _disable_msi, _disable_msix, _use_msg - fix for 16 byte CDBs, max_cmd_len should be initialized to 16. - bump the driver version. - add <pv-drivers at vmware.com> in the MAINTAINERS file. - rebase to 2.6.32-rc1. Changelog (v4-v3) - use size_t type for a loop iterator. - use IS_ALIGNED instead of ~PAGE_M...

...ic DEFINE_PCI_DEVICE_TABLE(vmci_ids) = { + {PCI_DEVICE(PCI_VENDOR_ID_VMWARE, PCI_DEVICE_ID_VMWARE_VMCI),}, + {0}, +}; + +static struct vmci_device vmci_dev; + +/* These options are false (0) by default */ +static bool vmci_disable_host; +static bool vmci_disable_guest; +static bool vmci_disable_msi; +static bool vmci_disable_msix; + +/* + * Allocate a buffer for incoming datagrams globally to avoid repeated + * allocation in the interrupt handler's atomic context. + */ +static uint8_t *data_buffer; +static u32 data_buffer_size = VMCI_MAX_DG_SIZE; + +/* + * If the VMCI hardware supports th...

...ic DEFINE_PCI_DEVICE_TABLE(vmci_ids) = { + {PCI_DEVICE(PCI_VENDOR_ID_VMWARE, PCI_DEVICE_ID_VMWARE_VMCI),}, + {0}, +}; + +static struct vmci_device vmci_dev; + +/* These options are false (0) by default */ +static bool vmci_disable_host; +static bool vmci_disable_guest; +static bool vmci_disable_msi; +static bool vmci_disable_msix; + +/* + * Allocate a buffer for incoming datagrams globally to avoid repeated + * allocation in the interrupt handler's atomic context. + */ +static uint8_t *data_buffer; +static u32 data_buffer_size = VMCI_MAX_DG_SIZE; + +/* + * If the VMCI hardware supports th...

Hello list, I have two differents installation Xen Hypervisor on two identical physical server, on the same switch : The problem is on my new server (Xen 4.0.1 with pvops kernel 2.6.32.24), I have bad performance on bandwidth I have test with a files copy and "iperf". Result iperf average: Transfert Bandwidth XEN-A -> Windows

Hello, I''m facing a strange issue with network card PCI passthrough on my openwrt test domU. - With network PCI passthrough, DNS lookup failed for some domains (exemple, google.com) but not for other (free.fr my ISP, or my domain jbfavre.org). I can ping an IP address without any problem. - Starting domU as a "normal" (ie without PCI passthrough), no problem. As far as I can

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication