> > Thanks for testing. I want to pass the changes by a couple other
> > people before I go ahead with a commit.
> >
> > Dave
> >
>
> Hi Dave,
>
> I was just wondering when these changes will hit the tree, I have been
> running your patch in production for some time now and all seems well.
J
Hello,
We've been using this patch in production on four servers for a number of
weeks, and it has worked 100%. Systems are all Dell R610, and run
7.2-RELEASE as well as 8.0-RELEASE.
Regards,
M. Jones
Tom Judge wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> David Christense
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Christensen wrote:
>>> Does the attached patch make a difference for you?
>> 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 an
> > Does the attached patch make a difference for you?
>
> 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 for testing. I want to pass the changes by a couple
o
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
> > 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
> Enterpr
> > 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
> > b
> > 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
> > b
David Christensen wrote:
Is there any progress on this issue? We can provide access
to hardware with this fault (Specifically the R610).
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
> Is there any progress on this issue? We can provide access
> to hardware with this fault (Specifically the R610).
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
David Christensen wrote:
Hi,
we have two new Dell R610 machines with four bce NICs (only
bce0 is connected at this time). I tried cold (power cycle in
iDRAC) and warm reboot (shutdown -r now), NIC is working on
every reboot, but I am still seeing messages:
bce0: /usr/src/sys/dev/bce/if_bce.c(15
David Christensen wrote:
Hi,
we have two new Dell R610 machines with four bce NICs (only
bce0 is connected at this time). I tried cold (power cycle in
iDRAC) and warm reboot (shutdown -r now), NIC is working on
every reboot, but I am still seeing messages:
bce0: /usr/src/sys/dev/bce/if_bce.c
Hi,
> we have two new Dell R610 machines with four bce NICs (only
> bce0 is connected at this time). I tried cold (power cycle in
> iDRAC) and warm reboot (shutdown -r now), NIC is working on
> every reboot, but I am still seeing messages:
>
> bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY writ
Tom Judge wrote:
Tom Judge wrote:
David Christensen wrote:
The next test is to diable the LOM's management firmware
but boot to
an active network.
After disabling the management firmware and doing 1 cold reboot and 3
warms all worked correctly.
After re enabling the firmware and doing 1 co
Tom Judge wrote:
David Christensen wrote:
The next test is to diable the LOM's management firmware
but boot to
an active network.
After disabling the management firmware and doing 1 cold reboot and 3
warms all worked correctly.
After re enabling the firmware and doing 1 cold reboot and 3
David Christensen wrote:
The next test is to diable the LOM's management firmware
but boot to
an active network. Get the User Diag utility at the bottom of
http://www.broadcom.com/support/ethernet_nic/netxtremeii.php.
Run the uxdiag utility with the command line:
"C:\>uxdiag -c 0 -mfw 0 -c 1
> > The next test is to diable the LOM's management firmware
> but boot to
> > an active network. Get the User Diag utility at the bottom of
> > http://www.broadcom.com/support/ethernet_nic/netxtremeii.php.
> > Run the uxdiag utility with the command line:
> > "C:\>uxdiag -c 0 -mfw 0 -c 1 -mfw
David Christensen wrote:
Can you try a different test? Power-on the system with the network
cable attached to an idle switch (i.e. keep all network
traffic from
being forwarded to the NIC during driver initialization). Does the
system power up successfully? Repeatedly? The problem I saw wa
> > Can you try a different test? Power-on the system with the network
> > cable attached to an idle switch (i.e. keep all network
> traffic from
> > being forwarded to the NIC during driver initialization). Does the
> > system power up successfully? Repeatedly? The problem I saw was
> > c
David Christensen wrote:
After fighting with the update process for a bit and then learning
about the live cycle manager I have managed to test the
R610 with the
5.0.9 firmware.
On the face of it, it seems that this resolves the issue.
After a reboot this morning the error has resurfaced and
> > After fighting with the update process for a bit and then learning
> > about the live cycle manager I have managed to test the
> R610 with the
> > 5.0.9 firmware.
> >
> > On the face of it, it seems that this resolves the issue.
> >
> After a reboot this morning the error has resurfaced and
Tom Judge wrote:
David Christensen wrote:
Thanks for the rapid response.
Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834
Will that work?
Yes, that release does include a good version of BCM5709 bootcode
(v5.06).
I couldn't really tell until I downloaded the file and lo
David Christensen wrote:
Thanks for the rapid response.
Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834
Will that work?
Yes, that release does include a good version of BCM5709 bootcode (v5.06).
I couldn't really tell until I downloaded the file and looked at the
tempor
Steven Hartland wrote:
On Tue, 27 Oct 2009 23:02:09 -
"Steven Hartland" mentioned:
If I understand the PR comments right, the code to support this PHY
should be present in 8.0. So you can start by trying out 8.0-RC1
ISO image (or USB stick image, fwiw).
Just tried 8.0RC2 no go, PHY sti
On Tue, 27 Oct 2009 23:02:09 -
"Steven Hartland" mentioned:
If I understand the PR comments right, the code to support this PHY
should be present in 8.0. So you can start by trying out 8.0-RC1
ISO image (or USB stick image, fwiw).
Just tried 8.0RC2 no go, PHY still not supported :(
On Tue, 27 Oct 2009 23:02:09 -
"Steven Hartland" mentioned:
> Sorry I typo'ed there, should have said bce, is that still relevant?.
>
> We haven't been able to install any version yet, so can't just
> try a kernel, no way of getting data on to the machine without
> a working netcard ;-)
>
>
Sorry I typo'ed there, should have said bce, is that still relevant?.
We haven't been able to install any version yet, so can't just
try a kernel, no way of getting data on to the machine without
a working netcard ;-)
Did this update include any updated PHY support for bce? As the
the precise er
udge
Cc: n...@freebsd.org
Cc: rwilli...@borderware.com
Cc: Gideon Naim
Subject: RE: bce(4) BCM5907 CTX write errors on 7.2 driver
Sent: 27 Oct 2009 17:18
> Thanks for the rapid response.
>
> Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834
>
> Will that work?
Yes,
On Tue, 27 Oct 2009 20:30:38 -
"Steven Hartland" mentioned:
> M610 is also broken due to unsupported bge revision :(
>
What bge revision do you have? I recently committed support
for new bge(4) chip revisions to HEAD, can you check, please,
if HEAD recognize this adapter correctly? You ca
> Thanks for the rapid response.
>
> Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834
>
> Will that work?
Yes, that release does include a good version of BCM5709 bootcode (v5.06).
I couldn't really tell until I downloaded the file and looked at the
temporary files inside.
David Christensen wrote:
Has anyone seen these errors before:
http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat=
The system is a Dell R610 and it happens on both cold and warm boots.
I am about to check a second chassis, and test with 8, and
will follow up after my tests.
Yes, I've
> Has anyone seen these errors before:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat=
>
> The system is a Dell R610 and it happens on both cold and warm boots.
>
> I am about to check a second chassis, and test with 8, and
> will follow up after my tests.
Yes, I've seen these error
to my page.
Tom
- Original Message - From: "Tom Judge"
To:
Cc: ; "Xin LI" ; "David
Christensen" ; ;
"Stanislav Sedov"
Sent: Tuesday, October 27, 2009 8:11 PM
Subject: Re: bce(4) BCM5907 CTX write errors on 7.2 driver
Tom Judge wrote:
M610 is also broken due to unsupported bge revision :(
Regards
Steve
- Original Message -
From: "Tom Judge"
To:
Cc: ; "Xin LI" ; "David Christensen" ; ;
"Stanislav Sedov"
Sent: Tuesday, October 27, 2009 8:11 PM
Subject: Re: bce(4
Tom Judge wrote:
Hi,
Has anyone seen these errors before:
http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat=
The system is a Dell R610 and it happens on both cold and warm boots.
I am about to check a second chassis, and test with 8, and will follow
up after my tests.
Here are my tes
Hi,
Has anyone seen these errors before:
http://www.freebsd.org/cgi/query-pr.cgi?pr=135836&cat=
The system is a Dell R610 and it happens on both cold and warm boots.
I am about to check a second chassis, and test with 8, and will follow
up after my tests.
Tom
_
36 matches
Mail list logo
