Bug#515052: ksplice-create fails to create tarball
Tim Abbott scrisse: > Hello, > This problem is caused by a bug in Ksplice 0.9.5 that was fixed in > the Ksplice 0.9.6 upstream release. I'm currently moving home and unstable queue is temporarily frozen due to lenny release, 0.9.6 will be uploaded as soon as both factors get less tricky (the first one in particular :). Ciao, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S.| lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer pgpvTKc4LsNdt.pgp Description: PGP signature
Bug#515052:
Hello, After starting from scratch, the process just worked fine. I think this bug is resolved. Thank you very much for your co-operation and patience. Really appreciate it. Ksplice is a big leap for Linux kernel advancement. Kushal Koolwal I do blog at http://blogs.koolwal.net/ > Date: Fri, 13 Feb 2009 17:42:36 -0500 > From: tabb...@mit.edu > To: kushalkool...@hotmail.com > CC: 515...@bugs.debian.org > Subject: RE: Bug#515052: > > On Fri, 13 Feb 2009, Kushal Koolwal wrote: > >> Yes, it somehow got compiled with "Quoth..." when I was trying different >> thing - like re-compiling kernel with default config file when my >> previous attempt to use ksplice-create failed as mentioned before. >> >> So in order to distinguish the process I deleted the source (2.6.26) in >> which "Quoth.." was compiled and I downloaded the a fresh copy of source >> again and this time I slightly modified the patch from the example to >> replace "Quoth" with "Quote" so that I know if the process worked or >> not. I guess may be this is too much confusingsorry about that. > > Right, well the problem is that Ksplice requires that you give it > precisely the running kernel source, and you gave it the running kernel > source without the "Quoth" patch applied. So, one of Ksplice's safety > checks aborted the upgrade. > > It should work if you were to use the correct running kernel source and > have your patch change "Quoth" to "Quote". > >> Should I just start fresh and see what happens? > > That might be easiest. > > -Tim Abbott _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515052:
On Fri, 13 Feb 2009, Kushal Koolwal wrote: > Yes, it somehow got compiled with "Quoth..." when I was trying different > thing - like re-compiling kernel with default config file when my > previous attempt to use ksplice-create failed as mentioned before. > > So in order to distinguish the process I deleted the source (2.6.26) in > which "Quoth.." was compiled and I downloaded the a fresh copy of source > again and this time I slightly modified the patch from the example to > replace "Quoth" with "Quote" so that I know if the process worked or > not. I guess may be this is too much confusingsorry about that. Right, well the problem is that Ksplice requires that you give it precisely the running kernel source, and you gave it the running kernel source without the "Quoth" patch applied. So, one of Ksplice's safety checks aborted the upgrade. It should work if you were to use the correct running kernel source and have your patch change "Quoth" to "Quote". > Should I just start fresh and see what happens? That might be easiest. -Tim Abbott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515052:
Yes, it somehow got compiled with "Quoth..." when I was trying different thing - like re-compiling kernel with default config file when my previous attempt to use ksplice-create failed as mentioned before. So in order to distinguish the process I deleted the source (2.6.26) in which "Quoth.." was compiled and I downloaded the a fresh copy of source again and this time I slightly modified the patch from the example to replace "Quoth" with "Quote" so that I know if the process worked or not. I guess may be this is too much confusingsorry about that. Should I just start fresh and see what happens? Thanks Kushal Koolwal I do blog at http://blogs.koolwal.net/ > Date: Fri, 13 Feb 2009 17:06:25 -0500 > From: tabb...@mit.edu > To: kushalkool...@hotmail.com > CC: 515...@bugs.debian.org > Subject: RE: Bug#515052: > > From looking at the debugging output, I'm guessing that the 2.6.26-ksplice > kernel that you compiled was compiled with the "Quoth the kernel" example > patch already applied. > > You should be able to confirm this fairly easily by seeing whether "Quoth > the kernel" appears in the output of "dmesg". > > -Tim Abbott > > On Fri, 13 Feb 2009, Kushal Koolwal wrote: > >> >> Hi Tim, >> >>> Are you running the kernel 2.6.26-ksplice as well as using it to be build >>> your update against? >> Yes, I was running 2.6.26-ksplice while doing ksplice-create and >> ksplice-apply process. Sorry I forgot to mentioned that in the steps >> previously listed. >> >>> If you send me the data stored in the debugging file when your run >>> ksplice-apply with debugging enabled >> Not sure where the debug output is stored, but I am attaching the debug >> messages from "dmesg" when I gave the command ksplice-apply --debug >> ./ksplice-kkda1whi.tar.gz >> >> Please see the attachment. >> >> Thank you once again for your prompt response. >> >> Kushal Koolwal >> >> I do blog at http://blogs.koolwal.net/ >> _ >> Windows Live™: E-mail. Chat. Share. Get more ways to connect. >> http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009 _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515052:
From looking at the debugging output, I'm guessing that the 2.6.26-ksplice kernel that you compiled was compiled with the "Quoth the kernel" example patch already applied. You should be able to confirm this fairly easily by seeing whether "Quoth the kernel" appears in the output of "dmesg". -Tim Abbott On Fri, 13 Feb 2009, Kushal Koolwal wrote: > > Hi Tim, > > > Are you running the kernel 2.6.26-ksplice as well as using it to be build > > your update against? > Yes, I was running 2.6.26-ksplice while doing ksplice-create and > ksplice-apply process. Sorry I forgot to mentioned that in the steps > previously listed. > > > If you send me the data stored in the debugging file when your run > > ksplice-apply with debugging enabled > Not sure where the debug output is stored, but I am attaching the debug > messages from "dmesg" when I gave the command ksplice-apply --debug > ./ksplice-kkda1whi.tar.gz > > Please see the attachment. > > Thank you once again for your prompt response. > > Kushal Koolwal > > I do blog at http://blogs.koolwal.net/ > _ > Windows Live™: E-mail. Chat. Share. Get more ways to connect. > http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009
Bug#515052:
Hi Tim, > Are you running the kernel 2.6.26-ksplice as well as using it to be build > your update against? Yes, I was running 2.6.26-ksplice while doing ksplice-create and ksplice-apply process. Sorry I forgot to mentioned that in the steps previously listed. > If you send me the data stored in the debugging file when your run > ksplice-apply with debugging enabled Not sure where the debug output is stored, but I am attaching the debug messages from "dmesg" when I gave the command ksplice-apply --debug ./ksplice-kkda1whi.tar.gz Please see the attachment. Thank you once again for your prompt response. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009 ksplice.debug Description: Binary data
Bug#515052:
Hi Kushal, Are you running the kernel 2.6.26-ksplice as well as using it to be build your update against? If you send me the data stored in the debugging file when your run ksplice-apply with debugging enabled ksplice-apply --debug ./ksplice-kkda1whi.tar.gz I can take a look at it. -Tim Abbott On Fri, 13 Feb 2009, Kushal Koolwal wrote: > > Hi Tim, > > So I made some progress after downloading the latest 0.9.6 version as > suggested by you. But now I got stuck at the ksplice-apply command. Here is > what I get: > > > make: Entering directory `/usr/src/linux-headers-2.6.26-ksplice' > INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi.ko > INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi_vmlinux-helper.ko > INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi_vmlinux.ko > make: Leaving directory `/usr/src/linux-headers-2.6.26-ksplice' > Ksplice update tarball written to ksplice-kkda1whi.tar.gz > > debian-sid:/usr/src/linux-source-2.6.26/kernel# ksplice-apply > ./ksplice-kkda1whi.tar.gz > Error applying Ksplice update kkda1whi: > Ksplice has aborted the upgrade because Ksplice has been unable to match the > object code produced by your current compiler and assembler against the > running > kernel's object code. If you provided the exact kernel source to the running > kernel, then it appears that your current compiler and/or assembler are > behaving differently from the compiler and assembler used to build the running > kernel. If possible, please use the exact compiler and assembler that were > used to build the running kernel. If you are using exactly the same compiler > and assembler, consider reporting a bug to de...@ksplice.com. > > Died at /usr/local/sbin/ksplice-apply line 131. > debian-sid:/usr/src/linux-source-2.6.26/kernel# > > Now the ksplice-create commands is able to successfully create the > tarball file. I am pretty sure that the kernel that I am using > (2.6.26-ksplice) is compiled with the same gcc version on my system. > Here is what I did to ensure that: > 0. apt-get update; apt-get upgrade > 1. I just downloaded the linux-source-2.6.26 from Debian Sid. > 2. Copied my default /boot/config-2.6.26-1-686 to the sources > linux-source-2.6.26 > 3. Compiled a new kernel called 2.6.26-ksplice (make-kpkg way) > > And then I followed the instructions as mentioned in my original bug report. > > Not sure if I missed any step or there is still some bug. > > Kushal Koolwal > > I do blog at http://blogs.koolwal.net/ > > > > > _ > Windows Live™: E-mail. Chat. Share. Get more ways to connect. > http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Faster_022009 > > >
Bug#515052:
Hi Tim, So I made some progress after downloading the latest 0.9.6 version as suggested by you. But now I got stuck at the ksplice-apply command. Here is what I get: make: Entering directory `/usr/src/linux-headers-2.6.26-ksplice' INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi.ko INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi_vmlinux-helper.ko INSTALL /tmp/ksplice-tmp-Q5Yl6u/kmodsrc/ksplice-kkda1whi_vmlinux.ko make: Leaving directory `/usr/src/linux-headers-2.6.26-ksplice' Ksplice update tarball written to ksplice-kkda1whi.tar.gz debian-sid:/usr/src/linux-source-2.6.26/kernel# ksplice-apply ./ksplice-kkda1whi.tar.gz Error applying Ksplice update kkda1whi: Ksplice has aborted the upgrade because Ksplice has been unable to match the object code produced by your current compiler and assembler against the running kernel's object code. If you provided the exact kernel source to the running kernel, then it appears that your current compiler and/or assembler are behaving differently from the compiler and assembler used to build the running kernel. If possible, please use the exact compiler and assembler that were used to build the running kernel. If you are using exactly the same compiler and assembler, consider reporting a bug to de...@ksplice.com. Died at /usr/local/sbin/ksplice-apply line 131. debian-sid:/usr/src/linux-source-2.6.26/kernel# Now the ksplice-create commands is able to successfully create the tarball file. I am pretty sure that the kernel that I am using (2.6.26-ksplice) is compiled with the same gcc version on my system. Here is what I did to ensure that: 0. apt-get update; apt-get upgrade 1. I just downloaded the linux-source-2.6.26 from Debian Sid. 2. Copied my default /boot/config-2.6.26-1-686 to the sources linux-source-2.6.26 3. Compiled a new kernel called 2.6.26-ksplice (make-kpkg way) And then I followed the instructions as mentioned in my original bug report. Not sure if I missed any step or there is still some bug. Kushal Koolwal I do blog at http://blogs.koolwal.net/ _ Windows Live™: E-mail. Chat. Share. Get more ways to connect. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_AE_Faster_022009 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515052: ksplice-create fails to create tarball
Ok thanks. I will try the upstream version on Debian Sid. Kushal Koolwal I do blog at http://blogs.koolwal.net/ > Date: Thu, 12 Feb 2009 19:49:22 -0500 > From: tabb...@mit.edu > To: kushalkool...@hotmail.com; 515...@bugs.debian.org > Subject: Re: Bug#515052: ksplice-create fails to create tarball > > Hello, > > This problem is caused by a bug in Ksplice 0.9.5 that was fixed in the > Ksplice 0.9.6 upstream release. > > -Tim Abbott _ Windows Live™: Keep your life in sync. http://windowslive.com/explore?ocid=TXT_TAGLM_WL_t1_allup_explore_022009
Bug#515052: ksplice-create fails to create tarball
Hello, This problem is caused by a bug in Ksplice 0.9.5 that was fixed in the Ksplice 0.9.6 upstream release. -Tim Abbott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515052: ksplice-create fails to create tarball
Package: ksplice
Version: 0.9.5-1
Severity: important
I was trying to follow the example at:
http://www.ksplice.com/example-update
This is what I did so far:
#cd /usr/src/
#apt-get install linux-source-2.6.26
#tar -xjvf linux-source-2.6.26.tar.bz2
#cd linux-source-2.6.26
#cp /boot/config-2.6.26-1-686 .config
#make xconfig
#mkdir ksplice
#cd ksplice/
#cp /boot/config-2.6.26-1-686 .config
#cp /boot/System.map-2.6.26-1-686 System.map
#ln -s /lib/modules/2.6.26-1-686/build
/usr/src/linux-source-2.6.26/ksplice/build
#cd ../kernel
#pwd
/usr/src/linux-source-2.6.26/kernel
#ksplice-create --patch=printk.patch /usr/src/linux-source-2.6.26
The first error message that I got was:
In file included from include/linux/gfp.h:4,
from include/linux/slab.h:12,
from include/linux/percpu.h:5,
from include/asm/local.h:4,
from include/linux/module.h:19,
from init/main.c:13:
include/linux/mmzone.h:18:26: error: linux/bounds.h: No such file or directory
include/linux/mmzone.h:197:5: warning: "MAX_NR_ZONES" is not defined
Then after searching on Internet I found that I need to give:
#make prepare
After doing the above, now I get the following error message:
#ksplice-create --patch=printk.patch /usr/src/linux-source-2.6.26
Starting kernel builds (this process might take a long time)...
scripts/kconfig/conf -s arch/x86/Kconfig
rm ksplice-revert-stamp
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CC init/main.o
/bin/sh: scripts/genksyms/genksyms: No such file or directory
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
Aborting: Prebuild failed at /usr/bin/ksplice-create line 180.
debian-sid:/usr/src/linux-source-2.6.26/kernel#
All the commands that I gave start with "#" symbol. Also I am attaching my
printk.patch file below:
--- linux-source-2.6.26/kernel/printk.c 2009-02-12 15:13:57.0 -0800
+++ linux-test/kernel/printk_patch.c2009-02-12 15:17:45.0 -0800
@@ -610,7 +610,8 @@
{
va_list args;
int r;
-
+
+ vprintk("Quoth the kernel:\n", NULL);
va_start(args, fmt);
r = vprintk(fmt, args);
va_end(args);
Thanks
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages ksplice depends on:
ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii gcc [c-compiler]4:4.3.2-3The GNU C compiler
ii gcc-4.1 [c-compiler 4.1.2-25 The GNU C compiler
ii gcc-4.2 [c-compiler 4.2.4-6 The GNU C compiler
ii gcc-4.3 [c-compiler 4.3.3-3 The GNU C compiler
ii libc6 2.7-18 GNU C Library: Shared libraries
ii patch 2.5.9-5 Apply a diff file to an original
ii perl5.10.0-19Larry Wall's Practical Extraction
ii rsync 3.0.5-1 fast remote file copy program (lik
ksplice recommends no packages.
ksplice suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
