From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751196AbWA2WNx (ORCPT ); Sun, 29 Jan 2006 17:13:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751197AbWA2WNx (ORCPT ); Sun, 29 Jan 2006 17:13:53 -0500 Received: from macferrin.com ([65.98.32.91]:30984 "EHLO macferrin.com") by vger.kernel.org with ESMTP id S1751196AbWA2WNx (ORCPT ); Sun, 29 Jan 2006 17:13:53 -0500 Message-ID: <43DD3DDF.6020901@macferrin.com> Date: Sun, 29 Jan 2006 15:12:47 -0700 From: Ken MacFerrin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jesper Juhl , s0348365@sms.ed.ac.uk, hugh@veritas.com CC: linux-kernel@vger.kernel.org Subject: Re: PROBLEM: kernel BUG at mm/rmap.c:486 - kernel 2.6.15-r1 References: <43DAE307.5010306@macferrin.com> <9a8748490601281031x514f0b9ckffcdce64148ebd8d@mail.gmail.com> In-Reply-To: <9a8748490601281031x514f0b9ckffcdce64148ebd8d@mail.gmail.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jesper Juhl wrote: > On 1/28/06, Ken MacFerrin wrote: > >>I started getting hard lockups on my desktop PC with the error "kernel >>BUG at mm/rmap.c:487" starting with kernel 2.6.13 and continuing through >>2.6.14. After switching to 2.6.15 the lockups have continued with the >>message "kernel BUG at mm/rmap.c:486". >> >>The frequency and circumstance are completely random which originally >>had me suspecting bad memory but after running Memtest86+ for over 12 >>hours without error I'm at a loss. >> >>I'm running the binary Nvidia driver so I'll understand if I can't get >>help here but in searching through the list archives it would seem I'm >>not alone and I am willing to try any patches that may help diagnose the >>issue. The crash happens at least daily and I've seen no difference in >>running kernels with or without PREEMPT enabled. >> > > If you don't actually *need* accelerated 3D (or if you could do > without it for a while), switching to the "nv" driver for a few > days/weeks would be interresting. If the crashes go away that would > point towards the nvidia driver, if they don't go away we'll get a > nice untainted crash report. > Thanks to all for the response. In hopes of helping to isolate this I will move back over to the "nv" driver to see if I can recreate the problem and get a clean bug report before applying Hugh's patch. This crash currently happens daily for me so I should be able to test this relatively quickly. -Ken