Thorsten
At 15:27 30.10.2004 -0700, you wrote:
I'm not 100% sure of what I did, but I remember a similar problem. I currently have:
CONFIG_SOFT_WATCHDOG=m
CONFIG_WD1100=m
and I only load WD1100 in /etc/modules. Reboot works by killing the watchdog process. I'm not happy with this set-up yet because the wd1100 gets loaded too late in the process. There are too many things that can go wrong before that in the boot process and then there's no watchdog to reset the system.
Agreed, there are a few things you can do:
- load wd1100 from initrd
- modify linuxrc so the right values to the control parameters are set early in the system set up
- and finally you could patch the wd1100 driver so it would reset the system as a default, be careful though, the wd1100 is a real hw watchdog. There is no way to stop him if your start up sequence takes more time.
cheers
Erich THINK
Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
