lkml.org 
[lkml]   [2006]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Fastboot] Kexec with latest kernel fail
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
-
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/

\
 
 \ /
  Last update: 2006-11-09 21:15    [W:0.041 / U:0.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site