> Anyway, got Voyage 0.7.5 working just fine now. Seems indeed like the > watchdog didn't work correctly, as on 0.7.5 the watchdog "pinger" starts > just after dnsmasq. On 0.8.0 the watchdog "pinger" never had a chance to > start, it seems.
youre booting with [ 31.367042] wd1100.c: a few hacks by erich.t...@think.ch root@voyage:~# modinfo wd1100 filename: /lib/modules/3.0.0-voyage/kernel/drivers/watchdog/wd1100.ko alias: char-major-10-130 description: National Semiconductor SC1x00 CPU watchdog driver author: Mark Grosberg <ma...@inprimis.com> and Rolando Goldman <rolan...@inprimis.com> license: GPL depends: intree: Y vermagic: 3.0.0-voyage SMP preempt mod_unload 486 parm: gcb:The GCB location (default is to look into the scratch pad) (int) parm: sysctl_wd_graceful:Graceful shutdown on close (int) parm: sysctl_wd_timeout:Watchdog timeout value in seconds (int) root@voyage:~# on 0.8.0 vs 0.7.5 check contents of /etc/modprobe.d/ALIX.conf (or whatever platform name is) 0.8.0 may be missing "wd1100" from the line. if it is missing, add it and retest. on my 4801, file is: root@voyage:~# more /etc/modprobe.d/4801.conf # # These lines generated automatically by copyfiles.sh, # parsing VOYAGE_SYSTEM_MODULES from Profile: 4801 # on Wed Nov 23 01:03:11 MST 2011 # options wd1100 sysctl_wd_graceful=0 sysctl_wd_timeout=30 options scx200_acb base=0x810,0x820 options pc87360 init=2 without "wd1100" in the line, the module will get the default, which might timeout and cause reboot before the watchdog daemon can run and reset it. this problem is fixed in daily-build you could try it. _______________________________________________ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
