bce(4) BCM5907 CTX write errors on 7.2 driver

[Tom Judge]

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 the 
>> box is again useless.
> 
> 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 caused by network traffic being handled by the NIC during driver
> initialization.  If you still see the same behavior then this might
> be a different issue.
> 

Looks like we are heading in the right direction here.

Setup:

R610[bce1]->Netgear 100/10 unmanaged switch-[uplink]->Managed server 
access switch.

The R610 is the only thing connected to the netgear switch.

When the uplink was severed during boot up it was reconnected after the 
link up event and while the NFS mounts where being mounted.

Cold reboots are with the server shutdown with the psu's remaining 
connected and then restarted.

Warm are just 'shutdown -r now'

Ice are from the psus disconnected from the mains supply.

These results are time ordered.

Type	Uplink	Result
Warm	No	Works
Warm	No	Works
Warm	No	Works
Cold	No	Works
Warm	No	Works
Cold	No	Works
Warm	No	Works
Ice	No	Works
Warn	No	Works
Ice	Yes	Works
Warm	Yes	Works
Cold	Yes	Works
Warm	Yes	Works
Ice	Bybass	Works	
Warm	Bypass	Fails
Cold	Bypass	Works - paniced on shutdown spin lock (sched) held to long pid 0
Cold	Bypass	Works
Warm	Bypass	Fails



We can provide full remote access to the following hardware (via 
enterprise drac) if required and on site hands if this will help get 
this issue resolved.

3 * R610
4 * R410
7 * R710


Tom