From: Nix <nix@esperi.org.uk>
To: Rob Landley <rob@landley.net>
Cc: zine el abidine Hamid <zine46@yahoo.fr>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at page_alloc.c:117!
Date: Thu, 08 Dec 2005 14:13:03 +0000 [thread overview]
Message-ID: <87d5k7vfrk.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200512052306.18420.rob@landley.net> (Rob Landley's message of "6 Dec 2005 05:11:12 -0000")
On 6 Dec 2005, Rob Landley whispered secretively:
> On Monday 05 December 2005 09:05, zine el abidine Hamid wrote:
>
>> PS : The user's manual definition of The Watch-Dog
>> Timer is : "a device to ensure thet standalone systems
>> can always recover from abnormal conditions that cause
>> the system to crash. These conditions may result from
>> an external EMI or software bug."
>
> Such as the power supply filling up with dust and catching fire.
>
> Rather an optimistic user's manual, really...
The Algol-68 people considered this problem long ago:
<http://gcc.gnu.org/ml/gcc-help/2004-11/msg00107.html>.
--
`Don't confuse the shark with the remoras.' --- Rob Landley
next prev parent reply other threads:[~2005-12-08 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051205133755.74679.qmail@web30613.mail.mud.yahoo.com>
2005-12-05 13:57 ` Kernel BUG at page_alloc.c:117! zine el abidine Hamid
2005-12-05 14:04 ` Arjan van de Ven
2005-12-05 14:25 ` zine el abidine Hamid
2005-12-05 14:28 ` Arjan van de Ven
2005-12-05 15:05 ` zine el abidine Hamid
2005-12-05 16:48 ` zine el abidine Hamid
2005-12-06 5:06 ` Rob Landley
2005-12-06 5:38 ` Keith Mannthey
2005-12-06 10:25 ` zine el abidine Hamid
2005-12-08 14:13 ` Nix [this message]
[not found] <1133870375.5334.9.camel@home.sweethome>
2005-12-07 9:40 ` zine el abidine Hamid
2005-12-07 10:10 ` Dirk Henning Gerdes
2005-12-05 13:16 zine el abidine Hamid
2005-12-05 13:25 ` Dirk Henning Gerdes
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=87d5k7vfrk.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=zine46@yahoo.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox