Date: Thu, 19 Nov 2009 16:49:18 -0800 From: "David Christensen" <davidch@broadcom.com> To: "Tom Judge" <tom@tomjudge.com> Cc: "net@freebsd.org" <net@freebsd.org>, "rwilliams@borderware.com" <rwilliams@borderware.com>, Miroslav Lachman <000.fbsd@quip.cz>, Gideon Naim <gideon.naim@broadcom.com> Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver Message-ID: <5D267A3F22FD854F8F48B3D2B52381933A20E0EFE1@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <4AFC862B.6060805@tomjudge.com> References: <4AE72910.8090708@tomjudge.com> <5D267A3F22FD854F8F48B3D2B52381933A04B49180@IRVEXCHCCR01.corp.ad.broadcom.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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I haven't been able to reproduce it on the r710 I have in house. > > Checking with other groups now to see if they have one a I can use,=20 > > though I'm not sure why the system would make a difference for this=20 > > particular issue. Just wanted to confirm that you're using=20 > the driver=20 > > built into the kernel (as opposed to a module) and that a warm boot=20 > > means running the "reboot" or "shutdown -r" > > commands while a cold boot means pressing the front panel=20 > power button=20 > > or using the DRAC to power down the system. > > Thanks for the update. >=20 > All these are true. >=20 > warm - shutdown -r now > cold - from the power button (iDRACs are not configured yet). >=20 > bce is compiled into the kernel (tested with GENERIC kernel=20 > from 8-RC2 as well as 7.1 with the 7.2 driver plus the split=20 > header patch). >=20 > For the record we also have not been able to reproduce the=20 > 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=20 Enterprise iDRAC module on your systems. Now that I have a failure again I have some ideas to test which might help. Stay tuned. Dave=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D267A3F22FD854F8F48B3D2B52381933A20E0EFE1>