public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch] min_low_pfn and max_low_pfn calcultion fix
Date: Mon, 12 Mar 2007 20:35:10 +0000	[thread overview]
Message-ID: <45F5B97E.2020607@sgi.com> (raw)
In-Reply-To: <1172619535.20006.334.camel@linux-znh>

Magnus Damm wrote:
> On 28 Feb 2007 07:38:55 +0800, Zou Nan hai <nanhai.zou@intel.com> wrote:
>>
[excessive text deleted]

>>   So it is better to fix and clean up those issues.
>> Calculate min_low_pfn and max_low_pfn in a consistent way.
>>
>> Below is the patch, please review and comments
>>
>> Signed-off-by:  Zou Nan hai <nanhai.zou@intel.com>
> 
> I've seen similar problems on a HP rx2620 box using 2.6.20. I managed
> to resolve that problem with a patch similar to this one, but then I
> realized that the issue I was seeing had been solved already by some
> mm-related patch by Bob Picco that got included in 2.6.21-rc1.

I tested on 2.6.21-rc3 with DEBUG_VM turned on. The vanilla 2.6.21-rc3
without Nan-hai's patch, panicked on bugcheck on free_initmem->free_page
as predicted. We still need this patch.

However, the zero-size vmcore problem is back on SN. But that is a
dfiffernet problem.

Regards,
 - jay


> 
> So, I suspect that 2.6.21-rc1 and rc2 should work just fine without this
> patch.
> 
> / magnus
> 
> PS. Any comments on the EFI_LOADER_DATA for ELF core header would be
> greatly appreciated, I think it is sort of related to this issue as
> well.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  parent reply	other threads:[~2007-03-12 20:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 23:38 [Patch] min_low_pfn and max_low_pfn calcultion fix Zou Nan hai
2007-02-28  1:48 ` Jay Lan
2007-02-28 10:01 ` Magnus Damm
2007-03-12 20:35 ` Jay Lan [this message]
2007-03-12 22:08 ` Luck, Tony
2007-03-13 19:28 ` Jay Lan
2007-03-14  4:38 ` Magnus Damm
2007-03-14 15:27 ` Jay Lan
2007-03-14 15:55 ` Jay Lan
2007-03-14 18:48 ` Jay Lan
2007-03-15  1:55 ` Horms
2007-03-15  2:11 ` Jay Lan
2007-03-16  5:15 ` Horms
2007-03-20 18:59 ` Jay Lan

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=45F5B97E.2020607@sgi.com \
    --to=jlan@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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