linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tabris <tabris@tabris.net>
To: Lawrence Walton <lawrence@the-penguin.otak.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: opps 2.4.20-pre5-ac2
Date: Sun, 8 Sep 2002 17:53:14 -0400	[thread overview]
Message-ID: <200209081753.14660.tabris@tabris.net> (raw)
In-Reply-To: <20020908203126.GA11475@the-penguin.otak.com>

This is an interaction of the rmap vm patch (included in -ac) and the nVidia 
binary driver. I have run into this myself, tho it doesn't usually cause a 
lockup for me. (instead, it puts kswapd in the Z state (it aparrently never 
respawns), and makes shutting down a PITA.))

Mind you, this is a bug in the nVidia driver, not the linux kernel, where it 
pulls a behaviour that never was really correct before, but did work. This 
bug truly needs to be reported to nVidia.

Not having that specific kernel tree on my system atm, I can't seem to find 
the line that is BUG()'ing. But iirc, it's in this set


        if (page->buffers)
                BUG();
        if (page->mapping)
                BUG();
        if (!VALID_PAGE(page))
                BUG();
        if (PageLocked(page))
                BUG();
        if (PageActive(page))
                BUG();
        page->flags &= ~((1<<PG_referenced) | (1<<PG_dirty));


and is the (page->mapping) test.

please, check your tree for the correct line (102 of page_alloc.c) to verify 
this, and then pass it along to nVidia.

--
tabris

  reply	other threads:[~2002-09-08 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-08 20:31 opps 2.4.20-pre5-ac2 Lawrence Walton
2002-09-08 21:53 ` Tabris [this message]
2002-09-09  0:19   ` Lawrence Walton
2002-09-09 21:09   ` Alan Cox
2002-10-01 12:56     ` 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=200209081753.14660.tabris@tabris.net \
    --to=tabris@tabris.net \
    --cc=lawrence@the-penguin.otak.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;
as well as URLs for NNTP newsgroup(s).