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:
append="panic=10" in /etc/lilo.conf
3. Schedule automatic reboot in case of impossible login
echo "/bin/sync; /sbin/reboot -f "|at now + 15min
4. Put "sysctl -w kernel.panic_on_oops=1" as early as possible
in your boot scripts[1].
And now reboot into the new kernel, try to login and delete the reboot
cronjob. If this doesn't work, just wait 15min and have the last stable kernel
booted automatically.
This method saved me and our customers a lot of time already :-)
Regards
Ingo Oeser
[1] This should be the default and should be disabled by the init scripts
as soon as we reach the desired runlevel (S99oops_not_fatal).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
