public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/rmap.c:480 in 2.6.10-rc3-bk7
Date: Wed, 15 Dec 2004 01:43:35 +0100	[thread overview]
Message-ID: <20041215004335.GX16322@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0412142304160.11826-100000@localhost.localdomain>

On Tue, Dec 14, 2004 at 11:26:48PM +0000, Hugh Dickins wrote:
> On Tue, 14 Dec 2004, Greg KH wrote:
> > 
> > So I finally try to get dri working on my laptop and I get the following
> > kernel bug when killing X (the program gish was running at the time):
> > 
> > kernel BUG at mm/rmap.c:480!
> > EIP is at page_remove_rmap+0x32/0x40
> > Process gish (pid: 10864, threadinfo=c8aea000 task=c7c2c040)
> >  [<c0141495>] zap_pte_range+0x135/0x290
> >...
> >  [<c0145f41>] exit_mmap+0x71/0x140
> >  [<c01163c4>] mmput+0x24/0x80
> >  [<c011a756>] do_exit+0x146/0x370
> >...
> 
> It's my BUG_ON(page_mapcount(page) < 0).
> 
> We've had about one report per month, over the last six months.
> But this is the first citing "gish"; sometimes it's been "cc1".
> 
> I've given it a lot of thought, but I'm still mystified.  The last
> report turned out to be attributable to bad memory; but this BUG_ON
> is too persistent and specific to be put down to that in all cases.

The killing X smells like it could be related to drm or other kernel X
drivers. Could you try not to load the drm/agp stuff and see if it goes
away?

      parent reply	other threads:[~2004-12-15  0:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 16:45 kernel BUG at mm/rmap.c:480 in 2.6.10-rc3-bk7 Greg KH
2004-12-14 23:26 ` Hugh Dickins
2004-12-15  0:10   ` Nick Piggin
2004-12-15  0:19   ` Greg KH
2004-12-15  1:11     ` Greg KH
2004-12-15 17:23       ` Hugh Dickins
2004-12-15 17:58         ` Greg KH
2004-12-15 18:48           ` Hugh Dickins
2004-12-15 22:22             ` Hugh Dickins
2004-12-15 22:33             ` Dave Airlie
2004-12-15 23:19               ` Greg KH
2004-12-15 19:03           ` Andrea Arcangeli
2004-12-15 22:48             ` Andrea Arcangeli
2004-12-15 23:41               ` Greg KH
2004-12-16  5:18                 ` Hugh Dickins
2004-12-16 14:28                   ` Andrea Arcangeli
2004-12-16 17:03                     ` Hugh Dickins
2004-12-15  0:43   ` Andrea Arcangeli [this message]

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=20041215004335.GX16322@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=hugh@veritas.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