> | > Specifically, we've seen that newer (9 and higher) have issues with
> | > the doing initial setup and negotiation and that Dell did indeed
> | > release newer firmware to fix the issues. This requires a full
> | > reboot into Linux (probably centos6) to get the update to execute.
> |
> | I c
On Fri, Apr 12, 2013 at 02:09:04PM -0700, Xin Li wrote:
| (Added David to Cc)
|
| On 04/12/13 13:56, Sean Bruno wrote:
| > A note from cluster...@freebsd.org
| >
| > It looks like there is some amount of instability or bugginess in
| > some of the Broadcom firmware(management) on the bce(4) chipe
On Fri, Apr 12, 2013 at 1:56 PM, Sean Bruno wrote:
> A note from cluster...@freebsd.org
>
> It looks like there is some amount of instability or bugginess in some
> of the Broadcom firmware(management) on the bce(4) chipeset shipped on
> later generations of the Poweredge 2950 from Dell:
>
> bce0:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
(Added David to Cc)
On 04/12/13 13:56, Sean Bruno wrote:
> A note from cluster...@freebsd.org
>
> It looks like there is some amount of instability or bugginess in
> some of the Broadcom firmware(management) on the bce(4) chipeset
> shipped on late
A note from cluster...@freebsd.org
It looks like there is some amount of instability or bugginess in some
of the Broadcom firmware(management) on the bce(4) chipeset shipped on
later generations of the Poweredge 2950 from Dell:
bce0:
Specifically, we've seen that newer (9 and higher) have issu
