Strange. Can you send me all your problematic binaries so that I can test by myself what kickstart is doing here?
Thanks, -Jan -- Jan Stoess KIT/UKa System Architecture Group Phone: +49 (721) 608-4056 Fax: +49 (721) 608-7664 http://os.ibds.kit.edu/stoess From: l4ka-boun...@ira.uni-karlsruhe.de [mailto:l4ka-boun...@ira.uni-karlsruhe.de] On Behalf Of Felipe Astroza Sent: Tuesday, March 30, 2010 11:56 PM To: l...@ira.uni-karlsruhe.de Subject: Re: Kickstart issue I've changed Makeconf.local CPU=k8 to CPU=p4 k8 produces a x86-kernel that cover a huge region. The new kernel works perfectly: KickStart 0.12.56 Detected multiboot compliant loader kernel (0x0011a000-0x0015477c) => 0x00b0d000 (0x0011a1a0-0x001336c0) -> 0x00400000-0x00419520 mods[0].start = 0x0011a000, mods[0].end = 0x0015477c mods[1].start = 0x00155000, mods[1].end = 0x0016ca2b mods[2].start = 0x0016d000, mods[2].end = 0x001d28e2 (0x001336c0-0x00133fc3) -> 0x00600000-0x00600903 mods[0].start = 0x0011a000, mods[0].end = 0x0015477c mods[1].start = 0x00155000, mods[1].end = 0x0016ca2b mods[2].start = 0x0016d000, mods[2].end = 0x001d28e2 (0x00134000-0x0013819a) -> 0x00800000-0x0080419a mods[0].start = 0x0011a000, mods[0].end = 0x0015477c mods[1].start = 0x00155000, mods[1].end = 0x0016ca2b mods[2].start = 0x0016d000, mods[2].end = 0x001d28e2 (0x001381a0-0x001445d0) -> 0x00a00000-0x00a0c430 mods[0].start = 0x0011a000, mods[0].end = 0x0015477c mods[1].start = 0x00155000, mods[1].end = 0x0016ca2b mods[2].start = 0x0016d000, mods[2].end = 0x001d28e2 (0x00145000-0x0014b790) -> 0x00b0d000-0x00b13790 mods[0].start = 0x0011a000, mods[0].end = 0x0015477c mods[1].start = 0x00155000, mods[1].end = 0x0016ca2b mods[2].start = 0x0016d000, mods[2].end = 0x001d28e2 the min=0x00400000 and max=0x00b13790, the bounds are CLOSER. I don't know why k8 kernel elf loads regions between 0x00400000-0x401075c8 (that's a headache) Cheers
