Meelis Roos wrote:
Unfortunatlety, 2.6.15 does not boot on this machine so I'm locked out
remotely at the moment.
Here it my paranoid boot setup:
Thanks, but it's not much use here, since the machine is a PReP powerpc
machine that can boot one kernel from disk (directly loaded from boot
Hi Meelis,
Unfortunatlety, 2.6.15 does not boot on this machine so I'm locked out
remotely at the moment.
Here it my paranoid boot setup:
1. Use lilo -R new-kernel, to boot a kernel only
once and reboot the default kernel next time.
2. Force reboot on any panic after 10 seconds:
Unfortunatlety, 2.6.15 does not boot on this machine so I'm locked out
remotely at the moment.
Here it my paranoid boot setup:
Thanks, but it's not much use here, since the machine is a PReP powerpc
machine that can boot one kernel from disk (directly loaded from boot
partition, no fancy
Ingo Oeser wrote:
Hi Meelis,
Unfortunatlety, 2.6.15 does not boot on this machine so I'm locked out
remotely at the moment.
Here it my paranoid boot setup:
1. Use lilo -R new-kernel, to boot a kernel only
once and reboot the default kernel next time.
2. Force reboot on any
4. Put sysctl -w kernel.panic_on_oops=1 as early as possible
in your boot scripts[1].
You can as well boot with oops=panic
-Andi
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi Andi,
Andi Kleen wrote:
4. Put sysctl -w kernel.panic_on_oops=1 as early as possible
in your boot scripts[1].
You can as well boot with oops=panic
Only on x86_64 as of Linux 2.6.16.
But maybe this could be put into kernel/panic.c instead :-)
Regards
Ingo Oeser
-
To unsubscribe
