bce(4) BCM5907 CTX write errors on 7.2 driver
davidch at broadcom.com
Fri Nov 20 00:56:10 UTC 2009
> > 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,
> > though I'm not sure why the system would make a difference for this
> > particular issue. Just wanted to confirm that you're using
> the driver
> > built into the kernel (as opposed to a module) and that a warm boot
> > means running the "reboot" or "shutdown -r"
> > commands while a cold boot means pressing the front panel
> power button
> > or using the DRAC to power down the system.
> Thanks for the update.
> All these are true.
> warm - shutdown -r now
> cold - from the power button (iDRACs are not configured yet).
> bce is compiled into the kernel (tested with GENERIC kernel
> from 8-RC2 as well as 7.1 with the 7.2 driver plus the split
> header patch).
> 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.
More information about the freebsd-net