public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paweł <anilatx@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/rmap.c:669 (during localegen)
Date: Fri, 02 May 2008 00:24:06 +0200	[thread overview]
Message-ID: <481A4306.5070701@gmail.com> (raw)
In-Reply-To: <261769053@web.de>

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� <anilatx () gmail ! com>
> 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:[<ffffffff80270c74>]
>>> [<ffffffff80270c74>] 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


  reply	other threads:[~2008-05-01 22:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-01 18:19 Re:Re: kernel BUG at mm/rmap.c:669 (during localegen) devzero
2008-05-01 22:24 ` Paweł [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-01 10:44 Paweł
2008-05-01 12:37 ` Hugh Dickins

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=481A4306.5070701@gmail.com \
    --to=anilatx@gmail.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