On 12/21/06, Larry Brigman <[EMAIL PROTECTED]> wrote:
> On 12/21/06, Horms <[EMAIL PROTECTED]> wrote:
> > On Thu, Dec 21, 2006 at 05:36:25PM +0900, Magnus Damm wrote:
> > >
> > > I would focus on getting kexec to work properly first if I were you.
> > > And when that is in place I would spend time on fixing up kdump. The
> > > kdump chain is pretty complex, and the kexec user space code is pretty
> > > hairy. So after fixing up kexec you need to make sure the kdump chain
> > > works. This is very similar to the work that we have been doing with
> > > out Xen port.
> > >
> > > Like I said - the kdump chain is pretty complex, but I've found myself
> > > spending way too much time on the kexec user space tool itself. Simon,
> > > I and other people on the list have lately been working on cleaning up
> > > the code base - so again - I strongly recommend you to build on that
> > > code.
> >
> > Hi Larry,
> >
> > After porting and reporting kexec to xen several times
> > on several architectures, my advice is to get UP (maxcpus=1 is fine)
> > kexec working first. Once thats working build up SMP and kdump support
> > like Magnus suggests.
> >
>
> If I have something that is compiled but won't load a kernel on kexec
> -l or kexec -p
> would that be related to the kexec-tools version?
>
> It looks a lot like earlier problems but everything seemed to be
> solved by changing
> addresses of the starting kernel and crashkernel.  Mine the starting kernel is
> at 64M and using [EMAIL PROTECTED]
> Here is the output of the kexec -p command
>
> kexec_load failed: Cannot assign requested address
> entry       = 0x1498 flags = 1
                        ^
Turns out I'm a little slow in figuring things out.  I had the problem
in front of me already.
wrong address for entry.  Tried the new kexec-testing tools from horms
repository but
it still gave me the same entry.

Have to go back to my kernel port and figure out why the build is not
setting the physical start address correctly.
_______________________________________________
fastboot mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/fastboot

Reply via email to