Dennis writes:
> >Not every case causes a panic either. This week, I had an instance of
> >an i686 box lock solid with a DFE-530TX net card. Rebooting/power
> >cycling it didn't recover it (despite it working for the past month
> >without any problems). It only started working again after I mov
>
>Not every case causes a panic either. This week, I had an instance of
>an i686 box lock solid with a DFE-530TX net card. Rebooting/power
>cycling it didn't recover it (despite it working for the past month
>without any problems). It only started working again after I moved
>it into a differ
Rogier Wolff wrote:
> Dennis wrote:
> > 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
At 05:30 PM 11/15/2000 +0100, Rogier Wolff wrote:
> > 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 c
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
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
network card driver) and
6 matches
Mail list logo
