my kexec experience
Posted May 5, 2004 19:20 UTC (Wed) by
tjw.org (guest, #20716)
Parent article:
Reboot Linux faster using kexec (developerWorks)
I've been using the kexec patches for a few months now with pretty good success.
I was able to upgrade from 2.6.2 -> 2.6.3 -> 2.6.4 -> 2.6.5 using
Randy Dunlap's patches:
http://developer.osdl.org/rddunlap/kexec/
That is to say I was able to install a new kernel and reboot my workstation without going all the way down to the BIOS/SCSI BIOS.
In my opinion there are still a lot of things that need fixing before this makes it into the mainline.
1) Video Mode Selection and Frame Buffer Console are broken. You need to use the default console or you'll get a mangled (or blank) console after
doing a kexec reboot.
2) The e100 ethernet driver doesn't work after kexec reboot "e100: eth%d: e100_eeprom_load: EEPROM corrupted". However, the compatible Becker driver eepro100 works fine on my system.
3) Sometimes all console messages get printed to every vitural tty after kexec reboot.
4) Nobody seems to be maintaining kexec-tools so you still have to hack the latest version to use the correct syscall number.
Also it would be great if there were some way skip probing new devices and instead maintain a known device table (as Randy mentioned in a recent [fastboot] mailing list post). Hell, if this could be implemented just for the SCSI drivers, I'de call it good enough since over half my reboot time is waiting for the SCSI driver to probe IDs.
(
Log in to post comments)