LWN: Comments on "Reboot Linux faster using kexec (developerWorks)" https://lwn.net/Articles/83498/ This is a special feed containing comments posted to the individual LWN article titled "Reboot Linux faster using kexec (developerWorks)". en-us Tue, 02 Sep 2025 11:33:50 +0000 Tue, 02 Sep 2025 11:33:50 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net still getting errors compiling kexec-tools 1.8 https://lwn.net/Articles/85070/ https://lwn.net/Articles/85070/ cyberic I try to compile it with gcc version 3.3.3 (Debian 20040429)<p>And I get these errors:<br>gcc -Wall -g -O2 -fno-strict-aliasing -I./util_lib/include -DVERSION='&quot;1.8&quot;' -DRELEASE_DATE='&quot;01 December 2002&quot;' -o objdir/kexec/kexec-syscall.o -c kexec/kexec-syscall.c<br>kexec/kexec-syscall.c: In function `reboot':<br>kexec/kexec-syscall.c:26: error: invalid register name `r0' for register variable<br>kexec/kexec-syscall.c:26: error: invalid register name `r1' for register variable<br>kexec/kexec-syscall.c:26: error: invalid register name `r2' for register variable<br>kexec/kexec-syscall.c:26: error: invalid register name `r3' for register variable<br>kexec/kexec-syscall.c:26: error: invalid register name `r0' for register variable<br>kexec/kexec-syscall.c:26: error: unknown register name `lr' in `asm'<br>kexec/kexec-syscall.c: In function `kexec_load':<br>kexec/kexec-syscall.c:27: error: invalid register name `r0' for register variable<br>kexec/kexec-syscall.c:27: error: invalid register name `r1' for register variable<br>kexec/kexec-syscall.c:27: error: invalid register name `r2' for register variable<br>kexec/kexec-syscall.c:27: error: invalid register name `r3' for register variable<br>kexec/kexec-syscall.c:27: error: invalid register name `r0' for register variable<br>kexec/kexec-syscall.c:27: error: unknown register name `lr' in `asm'<br>make: *** [objdir/kexec/kexec-syscall.o] Error 1<p>any help? Thu, 13 May 2004 15:44:28 +0000 my kexec experience https://lwn.net/Articles/84014/ https://lwn.net/Articles/84014/ tjw.org <pre> diff -urN kexec-tools-1.8.orig/kexec/kexec-syscall.c kexec-tools-1.8/kexec/kexec-syscall.c --- kexec-tools-1.8.orig/kexec/kexec-syscall.c 2002-11-18 00:58:05.000000000 -0600 +++ kexec-tools-1.8/kexec/kexec-syscall.c 2004-02-12 11:29:01.000000000 -0600 @@ -22,7 +22,7 @@ #define LINUX_REBOOT_CMD_KEXEC 0x45584543 -#define __NR_kexec_load 259 +#define __NR_kexec_load 274 _syscall4(int, reboot, int, magic1, int, magic2, int, cmd, void*, arg); _syscall4(long, kexec_load, void *, entry, unsigned long, nr_segments, struct kexec_segment *, segments, unsigned long, flags); </pre> Fri, 07 May 2004 15:02:07 +0000 my kexec experience https://lwn.net/Articles/83858/ https://lwn.net/Articles/83858/ hildeb Could you please post a patch for the syscall? Thu, 06 May 2004 17:37:51 +0000 Reboot Linux faster using kexec (developerWorks) https://lwn.net/Articles/83700/ https://lwn.net/Articles/83700/ snitm it will likely be merged if the core developer (Eric Biederman) takes some time to push it harder at Andrew Morton. Kexec has very minimal impact on the kernel and is quite a low risk patch. Randy Dunlap (at OSDL with Andrew) is quite active with maintaining current kexec patches as new releases of the 2.6 and 2.6-mm are made. Thu, 06 May 2004 04:26:50 +0000 my kexec experience https://lwn.net/Articles/83603/ https://lwn.net/Articles/83603/ tjw.org I've been using the kexec patches for a few months now with pretty good success.<p>I was able to upgrade from 2.6.2 -&gt; 2.6.3 -&gt; 2.6.4 -&gt; 2.6.5 using<br>Randy Dunlap's patches:<br>http://developer.osdl.org/rddunlap/kexec/<p>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.<p>In my opinion there are still a lot of things that need fixing before this makes it into the mainline.<p>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<br>doing a kexec reboot.<br>2) The e100 ethernet driver doesn't work after kexec reboot &quot;e100: eth%d: e100_eeprom_load: EEPROM corrupted&quot;. However, the compatible Becker driver eepro100 works fine on my system.<br>3) Sometimes all console messages get printed to every vitural tty after kexec reboot.<br>4) Nobody seems to be maintaining kexec-tools so you still have to hack the latest version to use the correct syscall number.<p>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.<p> Wed, 05 May 2004 19:20:58 +0000 Reboot Linux faster using kexec (developerWorks) https://lwn.net/Articles/83627/ https://lwn.net/Articles/83627/ hisdad One of the things linus wanted about kexec is the ability to boot something else. Such as a post mortem debugger.<p>Regards<br>Dad Wed, 05 May 2004 19:20:09 +0000 Reboot Linux faster using kexec (developerWorks) https://lwn.net/Articles/83599/ https://lwn.net/Articles/83599/ penguinroar What a wonderful thing, reboots after updates will go even faster and thats not bad in my opinion. The next step would be to be able to switch the kernel &quot;in motion&quot; but maybe thats not for a monolithic kernel to do. Anyway i hope it will work good enough to get into the main tree. Wed, 05 May 2004 18:34:04 +0000 Reboot Linux faster using kexec (developerWorks) https://lwn.net/Articles/83531/ https://lwn.net/Articles/83531/ Wills You covered kexec before in <A HREF="http://lwn.net/Articles/15468/">an LWN article in 2002</A> speculating that it might get merged with the main kernel - which still hasn't happened. Wed, 05 May 2004 15:23:19 +0000 Reboot Linux faster using kexec (developerWorks) https://lwn.net/Articles/83528/ https://lwn.net/Articles/83528/ horen <P> :) What a wonderful development! </P> <P> :( Too bad it's only for the 2.6-series kernels. </P> <P> I run FC/1 with an optimized 2.4.22-1.2188.nptl kernel on all our servers and workstations (yes, and mine here at home), and I'd love to have this ability to reboot them into a new kernel. I'm not so sure about moving immediately to FC/2 when it's released in the near-future, and I'm particularly not ready to move to LVM2 (IIRC, that's a "must-do" with the 2.6 kernel). </P> Wed, 05 May 2004 15:18:44 +0000