public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/21] random fixes
Date: Sun, 11 Aug 2002 20:40:31 -0700	[thread overview]
Message-ID: <3D572E2F.D7DE8DF9@zip.com.au> (raw)
In-Reply-To: 20020812025431.GA4429@www.kroptech.com

Adam Kropelin wrote:
> 
> FYI, just got this while un-tarring a kernel tree with 2.5.31+everything.gz:
> (no nvidia ;)
> 

That'll be this one:

	        BUG_ON(page->pte.chain != NULL);

we've had a few reports of this dribbling in since rmap went in.  But
nothing repeatable enough for it to be hunted down.

But we do have a repeatable inconsistency happening with ntpd and
memory pressure.  That may be related, but in that case it's probably
related to mlock().

So.  An open bug, alas.

  reply	other threads:[~2002-08-12  3:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-11  7:38 [patch 1/21] random fixes Andrew Morton
2002-08-11  7:56 ` Alexander Viro
2002-08-11 14:29 ` Adam Kropelin
2002-08-11 18:09   ` Andrew Morton
2002-08-12  0:27     ` Adam Kropelin
2002-08-12  0:41       ` Rik van Riel
2002-08-12  4:58       ` Andrew Morton
2002-08-13  0:26         ` Adam Kropelin
2002-08-13  0:49           ` Andrew Morton
2002-08-13  2:25             ` Adam Kropelin
2002-08-13  3:03               ` Andrew Morton
2002-08-13  4:10                 ` Adam Kropelin
2002-08-13  5:25                   ` Andreas Dilger
2002-08-13 12:37                     ` Adam Kropelin
2002-08-13 17:21                       ` Andreas Dilger
2002-08-13  5:32                   ` Andrew Morton
2002-08-13 15:39                     ` Daniel Egger
2002-08-14  0:01                     ` Adam Kropelin
2002-08-12  2:54     ` Adam Kropelin
2002-08-12  3:40       ` Andrew Morton [this message]
2002-08-14  8:35 ` William Lee Irwin III

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=3D572E2F.D7DE8DF9@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=akropel1@rochester.rr.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