Hello, Apologize for the typo in my previous post. I meant the work around I mentioned in the post is specific to MSI-X and is not required if the card does not support MSI-X. As I know, the BCM 5708 cards support only MSI and not MSI-X. And " Cat /proc/interrupts | grep eth0" can help in determining what the card supports.
Can you see the issue you are describing without passing this parameter ? With regards, Narendra K > -----Original Message----- > From: K, Narendra > Sent: Tuesday, June 01, 2010 10:49 PM > To: linux-poweredge-Lists > Subject: RE: Network issue on servers containing BCM 5709 / 5716 cards > resolved > > Hello, > > This issue I referred to in the below post is MSI-X specific and I > don't think BCM 5708 cards support MSI-X. This work aroud is not > required for the issue I described in the post. > > Cat /proc/interrupts | grep eth0 can tell you if it supports MSI or > MSI-X. > > With regards, > Narendra K > > > > > > > > -----Original Message----- > > > From: [email protected] [mailto:linux-poweredge- > > > [email protected]] On Behalf Of [email protected] > > > Sent: 25 May 2010 18:41 > > > To: [email protected] > > > Subject: Network issue on servers containing BCM 5709 / 5716 cards > > > resolved - > > > > > > Hello, > > > > > > Connectivity loss was observed under some heavy traffic conditions > on > > > RHEL 5.3/5.4/5.5 on servers containing BCM 5709/5716 cards. > > > > > > Work around: > > > > > > The issue is MSI-X specific. So passing "disable_msi=1" to the bnx2 > > > driver would prevent the issue from happening. > > > > RHEL 4.5 > > PE2950 > > Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit > > Ethernet (rev 12) > > > > # modinfo bnx2 > > filename: /lib/modules/2.6.9- > 55.ELsmp/kernel/drivers/net/bnx2.ko > > author: Michael Chan <[email protected]> > > description: Broadcom NetXtreme II BCM5706/5708 Driver > > license: GPL > > version: 1.4.43-rh 49524544DE69B4B5647379F > > parm: disable_msi:Disable Message Signaled Interrupt (MSI) > > vermagic: 2.6.9-55.ELsmp SMP 686 REGPARM 4KSTACKS gcc-3.4 > > depends: > > alias: pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i* > > alias: pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i* > > alias: pci:v000014E4d0000164Asv*sd*bc*sc*i* > > alias: pci:v000014E4d0000164Csv*sd*bc*sc*i* > > alias: pci:v000014E4d000016AAsv0000103Csd00003102bc*sc*i* > > alias: pci:v000014E4d000016AAsv*sd*bc*sc*i* > > alias: pci:v000014E4d000016ACsv*sd*bc*sc*i* > > > > With options bnx2 disable_msi=1 in modprobe.conf then > > # modprobe -r bnx2; modprobe bnx2 > > I get the following error and the NIC will not ifup - > > > > kernel: bnx2: eth1: Cannot allocate firmware buffer for > uncompression. > > > > I took the msi option out of modprobe.conf but the NIC would still > not > > ifup, even restarting the network service did not get the NIC back > > online. > > I ended up leaving the option out of modprobe.conf and rebooting the > > server for this to work ! > > > > I hope to set the disable_msi option on a clients server to overcome > a > > problem they are having, but I need to know why this error occurred > on > > my test box first. > > > > Any help appreciated, > > > > Cheers > > Nick . > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > signature database 5163 (20100601) __________ > > > > The message was checked by ESET NOD32 Antivirus. > > > > http://www.eset.com > > > > > > > > > > ------------------------------ > > > > Message: 6 > > Date: Tue, 1 Jun 2010 12:35:34 -0400 > > From: Drew Weaver <[email protected]> > > Subject: RE: Network issue on servers containing BCM 5709 / 5716 > cards > > resolved - > > To: "'Nick Lunt'" <[email protected]>, > > "[email protected]" <[email protected]> > > Message-ID: > > <[email protected]> > > Content-Type: text/plain; charset="us-ascii" > > > > Isn't this already fixed in the latest kernels? > > > > At least that is what I heard. > > > > thanks, > > -Drew > > > > > > -----Original Message----- > > From: [email protected] [mailto:linux-poweredge- > > [email protected]] On Behalf Of Nick Lunt > > Sent: Tuesday, June 01, 2010 11:36 AM > > To: [email protected] > > Subject: RE: Network issue on servers containing BCM 5709 / 5716 > cards > > resolved - > > > > Hi, > > > > > -----Original Message----- > > > From: [email protected] [mailto:linux-poweredge- > > > [email protected]] On Behalf Of [email protected] > > > Sent: 25 May 2010 18:41 > > > To: [email protected] > > > Subject: Network issue on servers containing BCM 5709 / 5716 cards > > > resolved - > > > > > > Hello, > > > > > > Connectivity loss was observed under some heavy traffic conditions > on > > > RHEL 5.3/5.4/5.5 on servers containing BCM 5709/5716 cards. > > > > > > Work around: > > > > > > The issue is MSI-X specific. So passing "disable_msi=1" to the bnx2 > > > driver would prevent the issue from happening. > > > > RHEL 4.5 > > PE2950 > > Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit > > Ethernet (rev 12) > > > > # modinfo bnx2 > > filename: /lib/modules/2.6.9- > 55.ELsmp/kernel/drivers/net/bnx2.ko > > author: Michael Chan <[email protected]> > > description: Broadcom NetXtreme II BCM5706/5708 Driver > > license: GPL > > version: 1.4.43-rh 49524544DE69B4B5647379F > > parm: disable_msi:Disable Message Signaled Interrupt (MSI) > > vermagic: 2.6.9-55.ELsmp SMP 686 REGPARM 4KSTACKS gcc-3.4 > > depends: > > alias: pci:v000014E4d0000164Asv0000103Csd00003101bc*sc*i* > > alias: pci:v000014E4d0000164Asv0000103Csd00003106bc*sc*i* > > alias: pci:v000014E4d0000164Asv*sd*bc*sc*i* > > alias: pci:v000014E4d0000164Csv*sd*bc*sc*i* > > alias: pci:v000014E4d000016AAsv0000103Csd00003102bc*sc*i* > > alias: pci:v000014E4d000016AAsv*sd*bc*sc*i* > > alias: pci:v000014E4d000016ACsv*sd*bc*sc*i* > > > > With options bnx2 disable_msi=1 in modprobe.conf then > > # modprobe -r bnx2; modprobe bnx2 > > I get the following error and the NIC will not ifup - > > > > kernel: bnx2: eth1: Cannot allocate firmware buffer for > uncompression. > > > > I took the msi option out of modprobe.conf but the NIC would still > not > > ifup, even restarting the network service did not get the NIC back > > online. > > I ended up leaving the option out of modprobe.conf and rebooting the > > server for this to work ! > > > > I hope to set the disable_msi option on a clients server to overcome > a > > problem they are having, but I need to know why this error occurred > on > > my test box first. > > > > Any help appreciated, > > > > Cheers > > Nick . > > > > > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > > signature database 5163 (20100601) __________ > > > > The message was checked by ESET NOD32 Antivirus. > > > > http://www.eset.com > > > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > > > > > ------------------------------ > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > > End of Linux-PowerEdge Digest, Vol 72, Issue 1 > > ********************************************** _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
