From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764777AbYEAWY4 (ORCPT ); Thu, 1 May 2008 18:24:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757079AbYEAWYt (ORCPT ); Thu, 1 May 2008 18:24:49 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]:25203 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751006AbYEAWYs (ORCPT ); Thu, 1 May 2008 18:24:48 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=ccPoM/s8neYcya36570xOfCA6nD3XCDv2aGui0VL0dwc6LuDQxA87dPwPRRE539JN+nymh0Q+jtLCSWWKf+6T+SqQOxbZvF7vmIYSLky5F8WCs+ofiecKg816+ofpHVyaJ1Zd5RZHH/nOUAyRukQDQ5AUYi5JhuGnGtRkUKyKt0= Message-ID: <481A4306.5070701@gmail.com> Date: Fri, 02 May 2008 00:24:06 +0200 User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080109) MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Re: kernel BUG at mm/rmap.c:669 (during localegen) References: <261769053@web.de> In-Reply-To: <261769053@web.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: =?UTF-8?B?UGF3ZcWC?= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Absolutely sure, renamed nvidia.ko(and checked after booting through lsmod) and hanged or restarted as always. I don't know why normal boot without this module and init=/bin/bash and manual start of klogd both leave completely nothing in logs(kern.log, messages and syslog, as these boots never happened) devzero@web.de wrote: > so, you are absolutely sure that this happens without nvidia driver? > > if not, rename the nvidia kernel module and try again..... > > >> (but this case leaves no logs becouse logging is down too) >> > > kernel logging should still be there (dmesg), but it may not go to /var/log/messages. > you may start syslogd/klogd manually in that runlevel > > > > > > > List: linux-kernel > Subject: Re:Re: kernel BUG at mm/rmap.c:669 (during localegen) > From: Pawe� > Date: 2008-05-01 13:54:56 > Message-ID: 4819CBB0.8010208 () gmail ! com > [Download message RAW] > > The problem is reproducible, as I wrote, also while booting through > init=/bin/bash parameter(and in init 1, but with hang instead of reboot) > so before loading any modules or nvidia drivers(but this case leaves no > logs becouse logging is down too) > I mentioned first and last line as commented, just to ensure that it's > everything about this symptome(timestamps suggest that) > > Hugh Dickins wrote: > >> On Thu, 1 May 2008, Pawe� wrote: >> >> >>> Every time I try to generate locales computer reboots or hangs. To ensure >>> that's not matter of graphDrivers I checked also in runlevel 1 and >>> "init=/bin/bash". >>> >>> Linux debby 2.6.25 #1 PREEMPT Mon Apr 28 15:18:31 CEST 2008 x86_64 GNU/Linux >>> gcc (GCC) 4.2.3 (Debian 4.2.3-3) >>> >>> [kern.log:] >>> //May 1 11:20:09 debby kernel: NVRM: bad caching on address >>> 0xffff81003a910000: actual 0x173 != expected 0x17b >>> >>> May 1 11:25:44 debby kernel: Eeek! page_mapcount(page) went negative! (-1) >>> May 1 11:25:44 debby kernel: page pfn = 257d2 >>> May 1 11:25:44 debby kernel: page->flags = 2200000000001c >>> May 1 11:25:44 debby kernel: page->count = 0 >>> May 1 11:25:44 debby kernel: page->mapping = 0000000000000000 >>> May 1 11:25:44 debby kernel: vma->vm_ops = 0x0 >>> May 1 11:25:44 debby kernel: ------------[ cut here ]------------ >>> May 1 11:25:44 debby kernel: kernel BUG at mm/rmap.c:669! >>> May 1 11:25:44 debby kernel: invalid opcode: 0000 [1] PREEMPT >>> May 1 11:25:44 debby kernel: CPU 0 >>> May 1 11:25:44 debby kernel: Modules linked in: nvidia(P) ... >>> May 1 11:25:44 debby kernel: Pid: 3007, comm: localedef Tainted: P >>> 2.6.25 #1 >>> May 1 11:25:44 debby kernel: RIP: 0010:[] >>> [] page_remove_rmap+0x164/0x180 >>> >>> >> Sorry, you'll have to ask Nvidia to help you with this: we don't >> know what their driver is up to, and don't have any "NVRM" errors in >> 2.6.25 source; they should be grateful for your reproducible test case. >> >> Hugh