From: Andi Kleen <ak@muc.de>
To: Andrew Morton <akpm@osdl.org>
Cc: ak@muc.de, linux-mm@kvack.org
Subject: Re: current -linus tree dies on x86_64
Date: 23 May 2004 16:33:31 +0200 [thread overview]
Date: Sun, 23 May 2004 16:33:31 +0200 [thread overview]
Message-ID: <20040523143331.GB33866@colin2.muc.de> (raw)
In-Reply-To: <20040523012149.68fcde6d.akpm@osdl.org>
On Sun, May 23, 2004 at 01:21:49AM -0700, Andrew Morton wrote:
> Andrew Morton <akpm@osdl.org> wrote:
> >
> > Andrew Morton <akpm@osdl.org> wrote:
> > >
> > > As soon as I put in enough memory pressure to start swapping it oopses in
> > > release_pages().
> >
> > I'm doing the bsearch on this.
>
> The crash is caused by the below changeset. I was using my own .config so
> the defconfig update is not the cause. I guess either the pageattr.c
> changes or the instruction replacements. The lesson here is to split dem
> patches up a bit!
>
> Anyway. Over to you, Andi.
Thanks for the report. Will look at it later tonight.
The only known problem right now is that the pageattr.c changes
seem to be miscompiled by the redhat compiler (but work with
other compilers). But this sounds differently.
I am still quite puzzled that this patch causes so many problems,
if you look through it most changes are harmless cleanups or
fixes only for very specific hardware configurations.
But to double check could you just revert the pageattr.c hunk
and see if that changes anything?
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-05-23 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 21:48 Andrew Morton
2004-05-23 6:58 ` Andrew Morton
2004-05-23 8:21 ` Andrew Morton
2004-05-23 14:33 ` Andi Kleen [this message]
2004-05-24 0:09 ` Andi Kleen
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=20040523143331.GB33866@colin2.muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.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