public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Don Zickus <dzickus@redhat.com>
Cc: "Lu, Yinghai" <yinghai.lu@amd.com>,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	ebiederm@xmission.com,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Kexec with latest kernel fail
Date: Thu, 09 Nov 2006 12:06:38 -0800	[thread overview]
Message-ID: <45538A4E.6040404@sgi.com> (raw)
In-Reply-To: <20061109163922.GE5622@redhat.com>

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
> 

  parent reply	other threads:[~2006-11-09 20:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  4:07 Kexec with latest kernel fail Lu, Yinghai
2006-11-09  5:48 ` [Fastboot] " Horms
2006-11-09  6:03   ` yhlu
2006-11-09  6:04   ` yhlu
2006-11-09  6:21     ` Horms
2006-11-09  7:36       ` Yinghai Lu
2006-11-10  0:47         ` Horms
2006-11-09 16:39 ` Don Zickus
2006-11-09 17:05   ` Yinghai Lu
2006-11-09 20:06   ` Jay Lan [this message]
2006-11-09 20:11     ` Vivek Goyal
  -- strict thread matches above, loose matches on Subject: below --
2006-11-10  1:12 Lu, Yinghai
2006-11-10  1:27 ` Horms
2006-11-10  1:41 Lu, Yinghai
2006-11-10  5:24 ` Eric W. Biederman
2006-11-10  7:30   ` yhlu
2006-11-10  9:18     ` Yinghai Lu
2006-11-10 20:01 Lu, Yinghai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45538A4E.6040404@sgi.com \
    --to=jlan@sgi.com \
    --cc=dzickus@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yinghai.lu@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox