-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 29.05.2010 00:25, Andres Aguirre wrote: > We add an emergency_restart(); I attach a patch
Sorry for upping an old discussion but it seems that the problem with the bcrm47xx watchdog wasn't fixed ever. Recently I had compiled the firmware for my D-Link DIR-320 using trunk rev.23109 snapshot. Playing with watchdog driver showed that it actually don't work. Symptoms are much the same as ones that were reported by Stefan Monnier. After killing watchdog process all I get in dmesg is: ... ... bcm47xx_wdt: Unexpected close, not stopping watchdog! bcm47xx_wdtWatchdog will fire soon!!! The unit itself remains functional: I can ping it, access through ssh, e.t.c. Looks like that for a some strange reason hardware reboot doesn't happen. I don't think that using the supplied patch is the right solution as it is pretty the same as if I would use the software watchdog driver. It will be great if other owners of devices based on Broadcom bcm47xx platform would check if the hardware watchdog is working as it should with their routers. I think that having properly functional hardware watchdog is very essential part of production-quality firmware. - -- Best regards, Alexey Loukianov mailto:[email protected] System Engineer, Mob.:+7(926)218-1320 *nix Specialist -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMna8BAAoJEPB9BOdTkBULlZ0IAJAKFcA+CiBtajOgIwNxo7zh 9X5bhvIrg5IN6SJ75o0ON95J5A5sWFwRlJvfI6H/TLOqErajn32csKb6XDNGXzuf x0MH2UUW3/tTRmFrIcPFnZT50nbskwVWDwfBR8/0PzjVSYFsVqogXuvUsHRdxAYB 0JGr6SBXgnVJsI2+NiNsakJ4oRMxRV17iYliiddWKxIX9z0Nx4sOBgFeGI09qCc+ KusKtyxjXi2j5Zqvaclxj3782EcReLglpv8Evk5uUltWrnhOVCxDYxx7+083BiSk Nwe0hYBQ3+IHmoc0o47taYlCUgm8Vj/0TeXGrDzrYVB/o2w9x7n5Xj/2ZnRRtqo= =VBsO -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
