From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261719AbULOAsI (ORCPT ); Tue, 14 Dec 2004 19:48:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261736AbULOApW (ORCPT ); Tue, 14 Dec 2004 19:45:22 -0500 Received: from mail-relay-1.tiscali.it ([213.205.33.41]:31690 "EHLO mail-relay-1.tiscali.it") by vger.kernel.org with ESMTP id S261791AbULOAoE (ORCPT ); Tue, 14 Dec 2004 19:44:04 -0500 Date: Wed, 15 Dec 2004 01:43:35 +0100 From: Andrea Arcangeli To: Hugh Dickins Cc: Greg KH , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: kernel BUG at mm/rmap.c:480 in 2.6.10-rc3-bk7 Message-ID: <20041215004335.GX16322@dualathlon.random> References: <20041214164548.GA18817@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-GPG-Key: 1024D/68B9CB43 13D9 8355 295F 4823 7C49 C012 DFA1 686E 68B9 CB43 X-PGP-Key: 1024R/CB4660B9 CC A0 71 81 F4 A0 63 AC C0 4B 81 1D 8C 15 C8 E5 User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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) > > [] zap_pte_range+0x135/0x290 > >... > > [] exit_mmap+0x71/0x140 > > [] mmput+0x24/0x80 > > [] 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?