From: devzero@web.de
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, Simon Arlott <simon@fire.lp0.eu>
Subject: Re: OT: Re: System reboot triggered by just reading a device file....!?
Date: Sat, 24 Nov 2007 00:07:47 +0100 [thread overview]
Message-ID: <4222353@web.de> (raw)
Hi Clemens,
>
> Hi, Roland!
>
> Please don't top-post.
sorry!
> > > [was: it would be easy to disable the kernel watchdog]
> > thanks, but i know i could do this.
>
> Good. I was also curious and just checked again. The watchdog subsystem
> is by default _disabled_ in the kernel configuration. If you use some
> distro's kernel, where they turned it on, complain to them!
> If you turned it on yourself, you are really on your own...
> the Kconfig help there is IMO sufficient and very clear and,
> "If unsure, say N". Hmm... sorry?!
whoops - sorry for that. i should have checked that, but i think i just didn`t expect some distro vendor to change that default.
sure i will complain to suse now. stopping getting on your nerves here, now.
> > this thread is not meant to protect myself from this curiousity but it is meant
> > to protect others. it`s a trap.
>
> I guess I understand your position. But I don't see no way to improve
> the kernel in that point.
> Complain to the guys who enabled the watchdog / setup this trap for
> any reason.
sure. you`re completely right.
> > i stepped into that.
> > now i know that trap, so i can easily sidestep.
> > it maybe very seldom that someone steps into this.
> > but it may happen and then someone will have trouble and spend time on this.
> > i think every admin can tell you about weird random reboots of his systems
> > which he cannot explain what was the reason for it.
>
> That's one possible way of "learning by doing suicide (tm);"
:)
> > this maybe some of those reasons and this one could be avoided.
> > i`m thinking of something simple like echo "now you`re armed" > /dev/watchdog
>
> Read some details about watchdogs to get more background and why the
> watchdog is triggered so easily and why it's good this way.
> i.e: http://www.ganssle.com/watchdogs.pdf
thanks for your help and for that very useful link. that`s the very best stuff i every read about watchdogs!
regards
Roland
__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
Mehr Infos unter http://produkte.web.de/club/?mc=021131
next reply other threads:[~2007-11-23 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 23:07 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-22 21:22 System reboot triggered by just reading a device file....!? devzero
2007-11-23 11:38 ` OT: " Clemens Koller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4222353@web.de \
--to=devzero@web.de \
--cc=clemens.koller@anagramm.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.