Hi Narendra, You seem to be pretty familiar with this problem - although I have not experienced it directly, it is a concern, and I would like to make sure I understand which systems may be affected by this issue.
You write: > 1. On RHEL 5.3 and RHEL 5.4, issue will not be seen if disable_msi=1 > parameter is passed to the native bnx2 driver(bnx2 driver version > 1.7.9-1) > 2. The issue will not be seen if bnx2 driver posted on support.dell.com > (bnx2 version >=1.8.7b) is used. I have R710 and R610 systems with BCM5709 running RHEL5.4 with bnx version: 1.9.3 and firmware-version: 4.6.4 NCSI 1.0.6 - these would seem to be potentially affected by this issue, but with the disable_msi=1 workaround should be okay. However, it isn't entirely clear to me what other systems may be affected by this problem: 1950/2950 systems with BCM5708 (RHEL5.4 with bnx version: 1.9.3 and firmware-version: 4.4.1 ipms 1.6.0) - presumably not, since these don't (appear to) support MSI-X, only MSI. R410 systems with BCM5716 - I don't have any of these (yet) - but it appears (from reports on this list) that they are susceptible to this problem as well, presumably because the 5716 does support MSI-X. It would be helpful in the deployment of a workaround to understand if this issue is only for MSI-X capable systems, or just certain BCM chips, or just Nehalem-architecture systems or what. @alex -- mailto:[email protected] _______________________________________________ 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
