Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Nov 2009 00:57:31 +0000
From:      Tom Judge <tom@tomjudge.com>
To:        David Christensen <davidch@broadcom.com>
Cc:        Gideon Naim <gideon.naim@broadcom.com>, "rwilliams@borderware.com" <rwilliams@borderware.com>, Miroslav Lachman <000.fbsd@quip.cz>, "net@freebsd.org" <net@freebsd.org>
Subject:   Re: bce(4) BCM5907 CTX write errors on 7.2 driver
Message-ID:  <4B0C80FB.5040901@tomjudge.com>
In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381933A20E0F332@IRVEXCHCCR01.corp.ad.broadcom.com>
References:  <4AE72910.8090708@tomjudge.com> <4AE76FF1.9010401@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B491AE@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE8CC59.7020004@tomjudge.com> <4AE9D10F.4040703@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A054DE883@IRVEXCHCCR01.corp.ad.broadcom.com> <4AE9F576.4060101@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35A55@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA0B11.2050209@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A19B35AB0@IRVEXCHCCR01.corp.ad.broadcom.com> <4AEA1183.7050306@tomjudge.com> <4AEB2571.7090006@tomjudge.com> <4AFAE428.5090907@quip.cz> <5D267A3F22FD854F8F48B3D2B52381933A20D4C55D@IRVEXCHCCR01.corp.ad.broadcom.com> <4AFAF542.8050004@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A20D4CA70@IRVEXCHCCR01.corp.ad.broadcom.com> <4AFC862B.6060805@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A20E0EFE1@IRVEXCHCCR01.corp.ad.broadcom.com> <5D267A3F22FD854F8F48B3D2B52381933A20E0F332@IRVEXCHCCR01.corp.ad.broadcom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
David Christensen wrote:
>>> For the record we also have not been able to reproduce the issue on 
>>> the R710 only the R610.
>> I got hold of an R610 system and I now understand why the 
>> issue was difficult to replicate on R710.  The R610 ships 
>> without Enterprise iDRAC while the R710 ship with the add-in 
>> Enterprise iDRAC module.  When the module is present the 
>> system is managed through the additional RJ45 port but when 
>> the module is absent iDRAC traffic will flow through the 
>> on-board 5709 adpaters.
>> The error will only occur when management firmware is loaded 
>> on the 5709 AND when NC-SI management functionality is enabled.
>>
>> You should be able to confirm this by adding or removing the 
>> Enterprise iDRAC module on your systems.  Now that I have a 
>> failure again I have some ideas to test which might help.
>> Stay tuned.
> 
> Does the attached patch make a difference for you?
> 
> FYI, I'll be out next week on vacation.
> 

Hi David,

This patch seems to do the trick, on at least one of the R610's that we 
have.

Just did cold boot, 5 warm boots, cold boot, 5 warm boots and have not 
had any issues.


Thanks

Tom



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B0C80FB.5040901>