https://bugzilla.novell.com/show_bug.cgi?id=343859 Summary: CONFIG_WATCHDOG defaults to "Y" for openSUSE/SLES Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: roland.kletzing@materna.de QAContact: qa@suse.de Found By: --- i had weird system reboots for no apparent reason and needed more then a hour to fix it. because i thought i had hit a kernel bug i investigated into this and found, that some app which only did _read_ requests accidentally triggered /dev/watchdog by just open/read/close on that device. turns out that watchdog is _ON_ by default on SuSE systems - even on my notebook. i think this is dangerous, because it`s against unix philosophy "reading is harmless". please take a look at : http://marc.info/?l=linux-kernel&m=119576660102941&w=2 http://marc.info/?l=linux-kernel&m=119581799925816&w=2 at least i think there are some people in this world who have also been caught by this trap. i know a lot of admins who whish they knew why this or that system rebooted. not sure if on their systems something also triggered the watchdog, but who knows.... whoever is in need of watchdog functionality, i think there aren`t many people ( <<5% ?? ), so i think it would be better to have this off by default. if kernel recompile is too much hassle to enable that, what about blacklisting all modules by default and make this a yast config option to explicitly enable watchdog functionality ? regards roland -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.