From: "David S. Miller" <davem@davemloft.net>
To: Martin Hicks <mort@sgi.com>
Cc: tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: bad pgd/pmd in latest BK on ia64
Date: Tue, 15 Mar 2005 18:40:35 +0000 [thread overview]
Message-ID: <20050315104035.40549ea8.davem@davemloft.net> (raw)
In-Reply-To: <20050315132458.GB19113@localhost>
On Tue, 15 Mar 2005 08:24:58 -0500
Martin Hicks <mort@sgi.com> wrote:
> It's also busted on ia64 in 2.6.11-mm3 if that narrows thing down.
Not necessary, we found the problem and the fix is in Linus's
tree. The clear_page_range() had to be restored to using
pgd_index() looping at the top level.
WARNING: multiple messages have this Message-ID (diff)
From: "David S. Miller" <davem@davemloft.net>
To: Martin Hicks <mort@sgi.com>
Cc: tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: bad pgd/pmd in latest BK on ia64
Date: Tue, 15 Mar 2005 10:40:35 -0800 [thread overview]
Message-ID: <20050315104035.40549ea8.davem@davemloft.net> (raw)
In-Reply-To: <20050315132458.GB19113@localhost>
On Tue, 15 Mar 2005 08:24:58 -0500
Martin Hicks <mort@sgi.com> wrote:
> It's also busted on ia64 in 2.6.11-mm3 if that narrows thing down.
Not necessary, we found the problem and the fix is in Linus's
tree. The clear_page_range() had to be restored to using
pgd_index() looping at the top level.
next prev parent reply other threads:[~2005-03-15 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 22:06 bad pgd/pmd in latest BK on ia64 Luck, Tony
2005-03-14 22:06 ` Luck, Tony
2005-03-14 22:34 ` David S. Miller
2005-03-14 22:34 ` David S. Miller
2005-03-14 23:11 ` David S. Miller
2005-03-14 23:11 ` David S. Miller
2005-03-14 23:31 ` David S. Miller
2005-03-14 23:31 ` David S. Miller
2005-03-15 7:17 ` Benjamin Herrenschmidt
2005-03-15 7:17 ` Benjamin Herrenschmidt
2005-03-15 13:24 ` Martin Hicks
2005-03-15 13:24 ` Martin Hicks
2005-03-15 18:40 ` David S. Miller [this message]
2005-03-15 18:40 ` David S. Miller
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=20050315104035.40549ea8.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mort@sgi.com \
--cc=tony.luck@intel.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 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.