From: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
To: Nathan Zimmer <nzimmer-sJ/iWh9BUns@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: BUG: unable to handle kernel paging request at 000000effd870020
Date: Wed, 02 Jan 2013 10:04:50 -0800 [thread overview]
Message-ID: <50E476C2.7060300@zytor.com> (raw)
In-Reply-To: <20130102172107.GA26761-3gyQo36HEq8TG1waqwXmH7Cf4lofQVJ7@public.gmane.org>
On 01/02/2013 09:21 AM, Nathan Zimmer wrote:
> I am getting an early boot problem. It only happens on the larger of the
> machines I haven't seen it crop up on machines with more then 512 GB of ram.
> It shows in the latest linus kernel too.
>
> I am (wildly) guessing that what is happening is that the new_memmap that is
> being passed to bios is somehow placed incorrectly.
> I have come up with a workaround. By placing it the DMA area the issue goes
> away but that doesn't seem like a real fix.
>
What does your memory map look like?
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Nathan Zimmer <nzimmer@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
matt.fleming@intel.com, tglx@linutronix.de, mingo@redhat.com
Subject: Re: BUG: unable to handle kernel paging request at 000000effd870020
Date: Wed, 02 Jan 2013 10:04:50 -0800 [thread overview]
Message-ID: <50E476C2.7060300@zytor.com> (raw)
In-Reply-To: <20130102172107.GA26761@gulag1.americas.sgi.com>
On 01/02/2013 09:21 AM, Nathan Zimmer wrote:
> I am getting an early boot problem. It only happens on the larger of the
> machines I haven't seen it crop up on machines with more then 512 GB of ram.
> It shows in the latest linus kernel too.
>
> I am (wildly) guessing that what is happening is that the new_memmap that is
> being passed to bios is somehow placed incorrectly.
> I have come up with a workaround. By placing it the DMA area the issue goes
> away but that doesn't seem like a real fix.
>
What does your memory map look like?
-hpa
next prev parent reply other threads:[~2013-01-02 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 17:21 BUG: unable to handle kernel paging request at 000000effd870020 Nathan Zimmer
2013-01-02 17:21 ` Nathan Zimmer
[not found] ` <20130102172107.GA26761-3gyQo36HEq8TG1waqwXmH7Cf4lofQVJ7@public.gmane.org>
2013-01-02 18:04 ` H. Peter Anvin [this message]
2013-01-02 18:04 ` H. Peter Anvin
[not found] ` <50E476C2.7060300-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2013-01-02 19:13 ` Nathan Zimmer
2013-01-02 19:13 ` Nathan Zimmer
[not found] ` <50E486E7.1080903-sJ/iWh9BUns@public.gmane.org>
2013-01-02 21:09 ` Robin Holt
2013-01-02 21:09 ` Robin Holt
[not found] ` <20130102210958.GD3470-sJ/iWh9BUns@public.gmane.org>
2013-01-03 15:50 ` Matt Fleming
2013-01-03 15:50 ` Matt Fleming
[not found] ` <1357228255.8203.10.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-01-03 22:07 ` Nathan Zimmer
2013-01-03 22:07 ` Nathan Zimmer
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=50E476C2.7060300@zytor.com \
--to=hpa-ymnouzjc4hwavxtiumwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=nzimmer-sJ/iWh9BUns@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.