If your blades are anything like mine, it will happen again. I agree it sounds like we're having similar issues, as are some others on the forums. Mine will get to 10.7, 11ish for a good couple hours, then switch proxies, and usually sit in the 300mh-2gh range for awhile, then switch and they die off and constantly reboot.

There's something not right in the firmware in my estimation. Sometimes, even on a cold boot, they just don't send packets out, and sometimes they do. Sometimes after not sending packets out for hours, they'll suddenly start. There's clearly a bug. It's happening on the new blades as well from what I've read in a few places, so it's not just a blade1 thing.

I have also noticed a pattern, if I disconnect blades from the network and let only one come online, generally speaking it works like a champ, 10-13gh. Within a minute or two of putting another blade on the same network (regardless of if its connecting to the same proxy/pool), they both go down. I continue to suspect something is up with how it's talking on the network.

Since this has occured, they seem most stable if they're allowed to hop between getwork and stratum (ie, put a getwork pool IP & a stratum proxy IP in the server line). If you force it to choose one or the other, it seems to simply fail to hash.

I see there's what appears to be a jtag/serial port on the NIC, I'm going to probe that tonight to see if I can find tty access.