From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Dennis <dennis@etinc.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>, linux-kernel@vger.kernel.org
Subject: Re: 2.4. continues after Aieee...
Date: Wed, 15 Nov 2000 17:30:29 +0100 (MET) [thread overview]
Message-ID: <200011151630.RAA04141@cave.bitwizard.nl> (raw)
In-Reply-To: <5.0.0.25.0.20001115111100.03572eb0@mail.etinc.com> from Dennis at "Nov 15, 2000 11:15:21 am"
Dennis wrote:
> At 02:53 AM 11/15/2000, Rogier Wolff wrote:
>
> >Shouldn't the system be "halted" after an "Aiee, killing interrupt
> >handler"?
> >
>
> This brings another question. Has there been any work done to force linux
> to reboot on all panics? Linux's propensity to crash drivers (say the
You already have the option to say what happens on panic.
> network card driver) and leave the system running make linux unusable in
> unattended environments as the machine is functionally dead.
Which doesn't help in this case, as your network card COULD be dead,
while the system simply hasn't crashed....
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* Common sense is the collection of *
****** prejudices acquired by age eighteen. -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-15 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 7:53 2.4. continues after Aieee Rogier Wolff
2000-11-15 16:15 ` Dennis
2000-11-15 16:30 ` Rogier Wolff [this message]
2000-11-16 11:20 ` Russell King
2000-11-16 15:34 ` Dennis
2000-11-16 16:11 ` Russell King
2000-11-16 4:51 ` David Feuer
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=200011151630.RAA04141@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=dennis@etinc.com \
--cc=linux-kernel@vger.kernel.org \
/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