From: Hugh Dickins <hugh@veritas.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
nickpiggin@yahoo.com.au, kernel@nn7.de
Subject: Re: 2.6.22.6: kernel BUG at fs/locks.c:171
Date: Tue, 9 Oct 2007 15:48:57 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710091544420.22005@blonde.wat.veritas.com> (raw)
In-Reply-To: <470B7D7E.5070901@wpkg.org>
On Tue, 9 Oct 2007, Tomasz Chmielewski wrote:
>
> I had a similar issue with 2.6.22.9, but as I had a proprietary nvidia module
> loaded, I didn't report it. X was not enabled, though.
There is indeed a strong likelihood that yours is
related to that nvidia(P): please take it to them.
Hugh
> Oct 3 10:14:09 tomek kernel: Eeek! page_mapcount(page) went negative! (-1)
> Oct 3 10:14:09 tomek kernel: page pfn = 13aa
> Oct 3 10:14:10 tomek kernel: page->flags = 40000400
> Oct 3 10:14:10 tomek kernel: page->count = 1
> Oct 3 10:14:10 tomek kernel: page->mapping = 00000000
> Oct 3 10:14:10 tomek kernel: vma->vm_ops = 0x0
> Oct 3 10:14:10 tomek kernel: ------------[ cut here ]------------
> Oct 3 10:14:10 tomek syslogd: /dev/tty12: Interrupted system call
> Oct 3 10:14:10 tomek kernel: kernel BUG at mm/rmap.c:628!
> Oct 3 10:14:10 tomek kernel: invalid opcode: 0000 [#1]
> Oct 3 10:14:10 tomek kernel: PREEMPT
> Oct 3 10:14:10 tomek kernel: Modules linked in: nvidia(P) ...
> Oct 3 10:14:10 tomek kernel: CPU: 0
> Oct 3 10:14:10 tomek kernel: EIP: 0060:[<c015a434>] Tainted: P VLI
> Oct 3 10:14:10 tomek kernel: EFLAGS: 00010246 (2.6.22.9-3 #1)
> Oct 3 10:14:10 tomek kernel: EIP is at page_remove_rmap+0xd7/0x105
next prev parent reply other threads:[~2007-10-09 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 13:09 Tomasz Chmielewski
2007-10-09 14:12 ` Soeren Sonnenburg
2007-10-09 14:48 ` Hugh Dickins [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-13 9:20 Soeren Sonnenburg
2007-09-12 23:51 ` Nick Piggin
2007-09-14 6:02 ` Soeren Sonnenburg
2007-09-13 21:22 ` Nick Piggin
2007-09-15 9:47 ` Soeren Sonnenburg
2007-09-15 10:22 ` Soeren Sonnenburg
2007-09-16 8:15 ` Nick Piggin
2007-09-17 13:43 ` Soeren Sonnenburg
2007-09-24 20:21 ` Soeren Sonnenburg
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=Pine.LNX.4.64.0710091544420.22005@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®