So we have to focus on b53 and GPIO number it uses. By default b53 takes a GPIO number from the nvram looking for "gpioN=robo_reset". This is the first weird thing. In the output of "nvram show" you provided I can't see such nvram entry It means that
bcm47xx_nvram_gpio_pin should return -ENOENT
b53_switch_get_reset_gpio should return -ENOENT
dev->reset_gpio should be set to -ENOENT
b53_switch_reset_gpio should never touch gpio because of dev->reset_gpio being negative number
I've also checked default NVRAM generated by CFE (I found WRT300Nv11-cfe.bin) and it also doesn't contain "gpioN=robo_reset". Maybe there was such entry earlier (only in "nvram" partition), but you or DD-WRT cleared the nvram? Or maybe there is some bug in b53/bcm47xx I can't notice?
Anyway, according to the CFE logs this router uses (for real) GPIO 8 to reset switch:
Reset switch via GPIO 8 ...
For years OpenWrt was using GPIO 2 to reset switch on WRT300N V1.1 (see r18921). Hauke in his patch simply copied that to b53. It appears to be wrong. My guess is that GPIO 2 reboots device as well. It was never triggered by broadcom-diag, because it didn't try to reset switch for the second time.
P.S.
I've temporary removed "gpio7=robo_reset" from my device and b53 stopped touching GPIOs. So I think there had to be some wrong entry in your nvram before installing DD-WRT.
(Last edited by Zajec on 13 Apr 2014, 11:22)