Re: Reboot problem.

[Willy Tarreau <willy@w.ods.org>]

Hello,

On Fri, Nov 04, 2005 at 01:33:01AM +0100, JaniD++ wrote:
> Hello list,
> 
> Is there any way to force reboot after this:
> 
> Nov  3 21:31:39 192.168.2.50 kernel: ------------[ cut here ]------------
> Nov  3 21:31:39 192.168.2.50 kernel: kernel BUG at mm/highmem.c:183!
> Nov  3 21:31:39 192.168.2.50 kernel: invalid operand: 0000 [#1]
> Nov  3 21:31:39 192.168.2.50 kernel: SMP
> Nov  3 21:31:39 192.168.2.50 kernel: Modules linked in: netconsole
> Nov  3 21:31:39 192.168.2.50 kernel: CPU:    3
(...)
> Nov  3 21:31:39 192.168.2.50 kernel: Code: e8 08 06 00 00 89 c7 e9 38 ff ff
> ff 55 89 e5 53 83 ec 04 89 c3 b8 80 6c 68 c0 e8 3e
> Nov  3 21:31:39 192.168.2.50 kernel:  <0>Fatal exception: panic in 5 seconds
> 
> At this point the system is freez, and only reset can help.

It should have rebooted, but the system is too instable to be able to
do so. In this case, the only thing that can help is a hardware watchdog.
Possibly, you motherboard includes a chipset with a watchdog that you can
simply enable by loading the module and having a simple daemon to ping it
(I have one which takes 12 kB of RAM and which tries mallocs, forks and
FS accesses).

If the daemon stops pinging the hardware watchdog for too long, the chipset
will simply assert the RESET signal and the system will reboot.

> Thanks
> 
> Janos

Regards,
Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/