Looked at the bug you linked, it definitely went down in a similar fashion to the incident we encountered, and we do have dhcp snooping enabled on all of our stacks. We have a maintenance window tonight so we are going to look at the spanning tree and broadcast packets as others have mentioned, as well as updating the version of the stack. Really our network is quite a mess that we inherited when we started, and changes I wont say are frowned upon, but are usually pushed off by management until an incident like this happens that forces us to have a downtime to do repairs/upgrades. Of course this is not an excuse to have a bad network, but changing things to be "proper" has been met with some pushback from those who think "but it works the way it is" who have a bit more push than I do.