mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: "Heiko Carstens" <Heiko.Carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at page_alloc.c:91! (2.4.19)
Date: Tue, 3 Sep 2002 19:31:52 +0200	[thread overview]
Message-ID: <E17mHWq-0005i3-00@starship> (raw)
In-Reply-To: <OF3A6E6F2C.2609CEE7-ONC1256C29.005E7DDC@de.ibm.com>

On Tuesday 03 September 2002 19:16, Heiko Carstens wrote:
> Hi,
> 
> >> Thanks for the patch but unfortunately it doesn't change the behaviour 
> at
> >> all. This BUG is still 100% reproducible by just having 1 process which
> >> allocates memory chunks of 256KB and after each allocation writes to 
> each
> >> of the pages in order to make them dirty.
> >Um, no smp --> no free race anyway.  But try the following instead, to
> >start narrowing down the possibilities:
> 
> Still the same BUG in __free_pages_ok happens, or in other words both of 
> your
> checks didn't catch the error...

My intention was to verify which one of the two possible execution paths
was taken, and also to verify that swap_duplicate doesn't see any problem
(there's a missing error check here).  Note that we also definitively
eliminated your original theory since we didn't arrive at the
page_cache_release via the if (page->mapping) path.

> Any other ideas?

Have you trimmed your config down to the absolute minimum?

Is there any such thing as kdb for S390?

-- 
Daniel

  reply	other threads:[~2002-09-03 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 17:16 Heiko Carstens
2002-09-03 17:31 ` Daniel Phillips [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-02 12:54 Heiko Carstens
2002-09-02 19:35 ` Daniel Phillips
2002-09-02  8:26 Heiko Carstens
2002-09-02 10:44 ` Daniel Phillips

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=E17mHWq-0005i3-00@starship \
    --to=phillips@arcor.de \
    --cc=Heiko.Carstens@de.ibm.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®