Re: [Fastboot] Kexec with latest kernel fail

Re: [Fastboot] Kexec with latest kernel fail

[Horms]

On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> Eric,
> 
> I got "Invalid memory segment 0x100000 - ..."
> using kexec latest kernel...

Which kernel? What config? What architecture? What hardware?

> Do I need patch for kexec tools with latest kexec in kernel?

Its largely dependant on what architecture you are using.
But try out kexec-tools-testing if you are not already doing so.
It is available via git from www.kernel.org/git

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

Re: [Fastboot] Kexec with latest kernel fail

[yhlu]

2.6.19 AMD64
1. kexec 2.6.17 AMD64 bzImage ? elf32 ( made by mkelfImage 2.5)
2. kexec suse 10.0 amd64 vmlinuz and initrd.

YH

On 11/8/06, Horms <horms@verge.net.au> wrote:
> On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> > Eric,
> >
> > I got "Invalid memory segment 0x100000 - ..."
> > using kexec latest kernel...
>
> Which kernel? What config? What architecture? What hardware?
>
> > Do I need patch for kexec tools with latest kexec in kernel?
>
> Its largely dependant on what architecture you are using.
> But try out kexec-tools-testing if you are not already doing so.
> It is available via git from www.kernel.org/git
>
> --
> Horms
>   H: http://www.vergenet.net/~horms/
>   W: http://www.valinux.co.jp/en/
>
> _______________________________________________
> fastboot mailing list
> fastboot@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/fastboot
>

Re: [Fastboot] Kexec with latest kernel fail

[yhlu]

On 11/8/06, Horms <horms@verge.net.au> wrote:
> On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> Its largely dependant on what architecture you are using.
> But try out kexec-tools-testing if you are not already doing so.
> It is available via git from www.kernel.org/git
It seems kexec-tools-testing can not be compiled.

YH

Re: [Fastboot] Kexec with latest kernel fail

[Horms]

On Wed, Nov 08, 2006 at 10:04:53PM -0800, yhlu wrote:
> On 11/8/06, Horms <horms@verge.net.au> wrote:
> >On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> >Its largely dependant on what architecture you are using.
> >But try out kexec-tools-testing if you are not already doing so.
> >It is available via git from www.kernel.org/git
> It seems kexec-tools-testing can not be compiled.

That is news to me, as I compiled it myself for all supported
architectures just yesterday.  What problem are you seeing?

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

Re: [Fastboot] Kexec with latest kernel fail

[Yinghai Lu]

.  ..  AUTHORS  config  configure.ac  COPYING  doc  .git  include
kdump  kexec  kexec_test  kexec-tools.spec.in  Makefile
Makefile.conf.in  News  purgatory  TODO  util  util_lib
yhlunb:/home/yhlu/xxx/xx/kernel/kexec-tools-testing # make
Makefile:2: Makefile.conf: No such file or directory
util_lib/Makefile:10: /util_lib/compute_ip_checksum.d: No such file or directory
util_lib/Makefile:10: /util_lib/sha256.d: No such file or directory
purgatory/Makefile:30: purgatory/arch//Makefile: No such file or directory
purgatory/Makefile:42: /purgatory/purgatory.d: No such file or directory
purgatory/Makefile:42: /purgatory/printf.d: No such file or directory
purgatory/Makefile:42: /purgatory/string.d: No such file or directory
kexec/Makefile:23: kexec/arch//Makefile: No such file or directory
make: execvp: ./AUTHORS: Permission denied
mkdir -p /kdump
cc   -M kdump/kdump.c | sed -e 's|kdump.o|/kdump/kdump.o|' > /kdump/kdump.d
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/crashdump.c | sed -e
's|crashdump.o|/kexec/crashdump.o|' > /kexec/crashdump.d
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/kexec-elf-boot.c | sed -e
's|kexec-elf-boot.o|/kexec/kexec-elf-boot.o|' >
/kexec/kexec-elf-boot.d
kexec/kexec-elf-boot.c:26:27: error: boot/elf_boot.h: No such file or directory
kexec/kexec-elf-boot.c:27:25: error: ip_checksum.h: No such file or directory
kexec/kexec-elf-boot.c:28:27: error: x86/x86-linux.h: No such file or directory
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/kexec-elf-rel.c | sed -e
's|kexec-elf-rel.o|/kexec/kexec-elf-rel.o|' > /kexec/kexec-elf-rel.d
kexec/kexec-elf-rel.c:8:27: error: boot/elf_boot.h: No such file or directory
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/kexec-elf-core.c | sed -e
's|kexec-elf-core.o|/kexec/kexec-elf-core.o|' >
/kexec/kexec-elf-core.d
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/kexec-elf-exec.c | sed -e
's|kexec-elf-exec.o|/kexec/kexec-elf-exec.o|' >
/kexec/kexec-elf-exec.d
kexec/kexec-elf-exec.c:8:27: error: boot/elf_boot.h: No such file or directory
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/kexec-elf.c | sed -e
's|kexec-elf.o|/kexec/kexec-elf.o|' > /kexec/kexec-elf.d
kexec/kexec-elf.c:8:27: error: boot/elf_boot.h: No such file or directory
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/ifdown.c | sed -e
's|ifdown.o|/kexec/ifdown.o|' > /kexec/ifdown.d
mkdir -p /kexec
cc   -Ikexec/arch//include -M kexec/kexec.c | sed -e
's|kexec.o|/kexec/kexec.o|' > /kexec/kexec.d
kexec/kexec.c:35:20: error: sha256.h: No such file or directory
kexec/kexec.c:40:26: error: arch/options.h: No such file or directory
make: *** No rule to make target `kexec/arch//Makefile'.  Stop.

Re: [Fastboot] Kexec with latest kernel fail

[Don Zickus]

On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> Eric,
> 
> I got "Invalid memory segment 0x100000 - ..."
> using kexec latest kernel...

I usually see this when people forget to add the "crashkernel=X@Y" into
their /etc/grub.conf kernel command line.  Where X and Y are arch
specific.

Cheers,
Don

Re: [Fastboot] Kexec with latest kernel fail

[Yinghai Lu]

just start from rc4 around.

YH

On 11/9/06, Don Zickus <dzickus@redhat.com> wrote:
> On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> > Eric,
> >
> > I got "Invalid memory segment 0x100000 - ..."
> > using kexec latest kernel...
>
> I usually see this when people forget to add the "crashkernel=X@Y" into
> their /etc/grub.conf kernel command line.  Where X and Y are arch
> specific.
>
> Cheers,
> Don
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Re: [Fastboot] Kexec with latest kernel fail

[Jay Lan]

Don Zickus wrote:
> On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
>> Eric,
>>
>> I got "Invalid memory segment 0x100000 - ..."
>> using kexec latest kernel...
> 
> I usually see this when people forget to add the "crashkernel=X@Y" into
> their /etc/grub.conf kernel command line.  Where X and Y are arch
> specific.

I have had "Invalid memory segment 0x4000000 - 0x4997fff" problem with
'-l' option _always_. Since my priority was on '-p' i did not spent time
on debugging this problem yet...

Maybe this "crashkerenl=X@Y" was the cause of my problem? Some platform
can not specify a location to load so that it is legal to only specify
"crashkernel=X" now. Is it possible '-l' code path still expect to
see Y?

Thanks,
 - jay

> 
> Cheers,
> Don
> 

Re: [Fastboot] Kexec with latest kernel fail

[Vivek Goyal]

On Thu, Nov 09, 2006 at 12:06:38PM -0800, Jay Lan wrote:
> Don Zickus wrote:
> > On Wed, Nov 08, 2006 at 08:07:22PM -0800, Lu, Yinghai wrote:
> >> Eric,
> >>
> >> I got "Invalid memory segment 0x100000 - ..."
> >> using kexec latest kernel...
> > 
> > I usually see this when people forget to add the "crashkernel=X@Y" into
> > their /etc/grub.conf kernel command line.  Where X and Y are arch
> > specific.
> 
> I have had "Invalid memory segment 0x4000000 - 0x4997fff" problem with
> '-l' option _always_. Since my priority was on '-p' i did not spent time
> on debugging this problem yet...
> 
> Maybe this "crashkerenl=X@Y" was the cause of my problem? Some platform
> can not specify a location to load so that it is legal to only specify
> "crashkernel=X" now. Is it possible '-l' code path still expect to
> see Y?
> 

kexec -l patch does not worry about crashkernel=. Only kexec -p path
does. So this is something else.

Thanks
Vivek

Re: [Fastboot] Kexec with latest kernel fail

[Horms]

On Wed, Nov 08, 2006 at 11:36:16PM -0800, Yinghai Lu wrote:
> .  ..  AUTHORS  config  configure.ac  COPYING  doc  .git  include
> kdump  kexec  kexec_test  kexec-tools.spec.in  Makefile
> Makefile.conf.in  News  purgatory  TODO  util  util_lib
> yhlunb:/home/yhlu/xxx/xx/kernel/kexec-tools-testing # make
> Makefile:2: Makefile.conf: No such file or directory
> util_lib/Makefile:10: /util_lib/compute_ip_checksum.d: No such file or 
> directory

You need to run ./configure before you run make,
I think that will make your problem go away

# ./configure && make

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

RE: [Fastboot] Kexec with latest kernel fail

[Lu, Yinghai]

There is no configure in kexec-tools-testing

YH

Re: [Fastboot] Kexec with latest kernel fail

[Horms]

On Thu, Nov 09, 2006 at 05:12:08PM -0800, Lu, Yinghai wrote:
> There is no configure in kexec-tools-testing

Sorry, you need to generate it from configure.ac by running autoconf

# autoconf && ./configure && make

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

RE: [Fastboot] Kexec with latest kernel fail

[Lu, Yinghai]

Thanks, It compiled

kexec get the same error "Invalid memory segment 0x100000 - ...."

YH

Re: [Fastboot] Kexec with latest kernel fail

[Eric W. Biederman]

"Lu, Yinghai" <yinghai.lu@amd.com> writes:

> Thanks, It compiled
>
> kexec get the same error "Invalid memory segment 0x100000 - ...."

Could you post the entire message and the contents of /proc/iomem.

That is where the compare is happening so this may be a parsing
issue of /proc/iomem.

Eric

Re: [Fastboot] Kexec with latest kernel fail

[yhlu]

I found the cause before your mail.

the /proc/iomem doesn't show RAM above 1M.

I have increased linuxbios table at high 0xf0000-0xf0400 to
0xf0000-0x100000. the RAM above 1M show up.

I think root cause in the latest kernel 2.6.19, e820 align increase to 0xffff.
and when it check 0xf0000-0xf0400, will make 0xf0000-0x100000
reserved, and then when it  check 0xf0400-4G, it will fail to reserved
System RAM above 1M.

I will check arch/x86_64/kernel/e820.c about
void __init e820_reserve_resources(void)
tommorrow.

YH

Re: [Fastboot] Kexec with latest kernel fail

[Yinghai Lu]

Andi,

On 11/9/06, yhlu <yinghailu@gmail.com> wrote:
> the /proc/iomem doesn't show RAM above 1M.
>
> I have increased linuxbios table at high 0xf0000-0xf0400 to
> 0xf0000-0x100000. the RAM above 1M show up.
>

Can you explain more about the patch?

I wonder what we suppose to do about [640K, 1M).
In LinuxBIOS we only set [0xa0000, 0xc0000) and [0xf0000, 0xf0400) to reserved,
[0xc0000, 0xf0000) and [0xf0400, 4G) as ram..

with your patch, the 1M above range will not show up on /proc/iomem

YH

[PATCH] Don't force reserve the 640k-1MB range
>From i386 x86-64 inherited code to force reserve the 640k-1MB area.
That was needed on some old systems.

But we generally trust the e820 map to be correct on 64bit systems
and mark all areas that are not memory correctly.

This patch will allow to use the real memory in there.

Or rather the only way to find out if it's still needed is to
try. So far I'm optimistic.

http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=dbf9272e863bf4b17ee8e3c66c26682b2061d40d

RE: [Fastboot] Kexec with latest kernel fail

[Lu, Yinghai]

in e820_reserves request_resource for 0xf0000-0xf03ff for reserve and
0xf0400-4G, will return busy with system_rom_resource (0xf0000-0xfffff)
that is put in the resources list by probe_roms,

We need to add back the patch for e820. otherwise all box with old
linuxbios will be broken to get correct in /proc/iomem in x86_64. and
can not use kexec any more.

Comments?

YH