**** BEGIN LOGGING AT Wed Jan 16 02:59:59 2013 Jan 16 08:47:38 hi nareshbhat Jan 16 08:52:33 ant_work: Hi Jan 16 08:54:45 If I try to use to ramdisk image I am getting the following error Jan 16 08:55:17 kexec -l zImage --initrd=ramdisk.img --command-line="root=/dev/ram rw ip=dhcp console=ttyAMA0,38400n8 init=/bin/bash" or Jan 16 08:55:17 kexec -l zImage --ramdisk=ramdisk.img --command-line="root=/dev/ram rw ip=dhcp console=ttyAMA0,38400n8 init=/bin/bash" Jan 16 08:55:35 The error is "Base address: 809de380 is not page aligned" Jan 16 08:55:40 any idea ? Jan 16 09:10:59 actually I'm not using initrd/ramdisk Jan 16 09:11:14 I remember ther have been some patches related, though Jan 16 09:11:59 i.e. [PATCH - kexec] arm: place initrd to safer place according to zImage length Jan 16 09:12:20 but long ago, in 2010, when we were testing uImages Jan 16 09:15:36 can you test using --initrd instead of ramdisk? Jan 16 09:16:36 oh, sorry, I see Jan 16 09:17:56 back in 2010 there have been other fixes, like [PATCH v2 1/3] Ramdisk address was not copied correctly on kexec'ed kernel Jan 16 09:18:08 sound like you're hitting a similar bug... Jan 16 09:28:56 nareshbhat: out ouf curiosity, what happpens if you load a true initramfs ( i.e. a cpio.gz) ? Jan 16 09:39:50 I will check Jan 16 09:50:47 getting same Jan 16 09:52:09 I will do send a e-mail to community Jan 16 10:12:54 Jay7: automake 1.13 -> +-AM_CONFIG_HEADER(config.h) Jan 16 10:12:54 ++AC_CONFIG_HEADERS(config.h) Jan 16 10:13:02 I'll send a patch Jan 16 10:13:34 ant_work: will it work with older automake? Jan 16 10:13:56 I'm just thinking about that. There is a bunch of fixes for oe-core Jan 16 10:14:17 so I assume it's tested :) Jan 16 10:14:52 Add obsolete_automake_macros.patch that replaces automake macros no longer supported by automake-1.13 with modern constructs. Jan 16 10:16:10 Jay7: about that new fork for HP Touchpad Jan 16 10:16:38 I've seen your link Jan 16 10:16:41 splitting the commit in it's different parts, I only see they remove root= rootfs= Jan 16 10:16:51 they somehow add lvml2 Jan 16 10:17:29 I'm sure they don't know that it's possible to override it by root= in cmdline Jan 16 10:17:44 lright, I concluded the same Jan 16 10:17:48 :) Jan 16 10:18:18 not sure about lvm2 Jan 16 10:18:24 may be it's not in kernel Jan 16 10:18:35 we doing no modules scan this time Jan 16 10:18:58 so.. --mem-max is only reasonable thing Jan 16 10:19:04 yes, the extra tags Jan 16 10:19:14 ah, I didn't understand Jan 16 10:19:18 - strcat(str_mtd_id, item->device+strlen(item->device)-1); Jan 16 10:19:18 258 Jan 16 10:19:18 + (str_mtd_id, item->device+strlen(item->device)-1); Jan 16 10:19:22 ah, yes Jan 16 10:19:38 this should break compiler imho Jan 16 10:20:04 https://github.com/willcast/kexecboot/blob/e832a06be24b56373161c0051e63638b1e182b9d/kexecboot.c#L258 Jan 16 10:20:13 this is how it looks now Jan 16 10:20:48 I was wondering about some strange assignment... Jan 16 10:20:53 seems an error to me Jan 16 10:57:37 Jay7: btw ka6sox crew is playing with nexus7 and kexecboot Jan 16 11:03:47 bluelightning: I've built with buildhistory and PR Server, this evening I should see if really there are rebuild issues Jan 16 11:54:32 ant_work: cool Jan 16 12:42:15 Jay7: do we discussed about having extra kexec opts in /boot.cg ? Jan 16 12:42:21 err.. Jan 16 12:42:29 did we discuss... Jan 16 12:46:24 seems this is good idea Jan 16 12:46:37 now I see real use case at least Jan 16 13:03:08 Jay7: I plan to upload the binaries of kexecboot-klibc static for x86/32,armv4 and maybe armv5te. Maybe it's better to upload the .cpio Jan 16 13:04:39 ..but there is old kexec there Jan 16 15:11:55 bluelightning: btw, BBFILE_PRIORITY_meta-initramfs = "8" and BBFILE_PRIORITY_meta-handheld = "7" Jan 16 15:12:11 hm.. BBFILE_PRIORITY_core = "5" Jan 16 15:12:46 ant_work: does it matter though? Jan 16 15:12:58 not much but it's not logical :) Jan 16 15:14:58 as long as we require meta-initramfs we should be able to 'override' it Jan 16 15:15:15 little point, though **** ENDING LOGGING AT Thu Jan 17 03:00:00 2013