From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Hugh Dickins <hugh@veritas.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: Top kernel oopses/warnings for the week of May 30th 2008
Date: Fri, 30 May 2008 15:34:20 -0700 [thread overview]
Message-ID: <484080EC.9090707@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0805301517500.3141@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Fri, 30 May 2008, Arjan van de Ven wrote:
>> ok for some it did gather this information, and it is
>>
>> kernel BUG at mm/highmem.c:319!
>
> That's just _odd_. The call chain actually has kmap() in it, and kmap
> does:
>
> if (!PageHighMem(page))
> return page_address(page);
> return kmap_high(page);
>
> so if it's the one at line 319, which says
>
> BUG_ON(!PageHighMem(page));
>
> then I wonder what happened to that PageHighMem() test of the page in
> between..
>
> Ahh.. Not the same "page". It looks like it's in the
> flush_all_zero_pkmaps() path, and it's clearing some _other_ page in the
> pkmap table in order to make room for the new one. So the page that causes
> problems is from here:
>
> page = pte_page(pkmap_page_table[i]);
>
> rather than the one we're trying to map.
>
> Not that it explains the BUG_ON(). We should only insert page table
> entries into the pkmap_page_table[] array in map_new_virtual(), which in
> turn is only called from kmap_high(), which in turn means that *those*
> pages have also gine through the PageHighMem() test.
>
> So it sounds like we either
> - have corruption in pkmap_page_table[]
> - or pte_page() doesn't reverse mk_pte(page) propely, and one or the
> other is broken.
>
> Does anybody know if the fc9 x86-32 kernel is built with PAE enabled?
versions that do identify themselves as "2.6.25-14.fc9.i686.PAE", and these ones didn't,
(they're all in the "2.6.25-14.fc9.i686" form) so this is a kernel without PAE.
next prev parent reply other threads:[~2008-05-30 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 16:39 Top kernel oopses/warnings for the week of May 30th 2008 Arjan van de Ven
2008-05-30 19:19 ` Hugh Dickins
2008-05-30 21:43 ` Linus Torvalds
2008-05-30 21:49 ` Arjan van de Ven
2008-05-30 22:17 ` Arjan van de Ven
2008-05-30 22:00 ` Arjan van de Ven
2008-05-30 22:30 ` Linus Torvalds
2008-05-30 22:34 ` Arjan van de Ven [this message]
2008-05-30 22:55 ` Linus Torvalds
2008-05-31 0:41 ` Dave Jones
2008-06-02 23:44 ` Hugh Dickins
2008-06-03 0:00 ` Andrew Morton
2008-06-03 0:41 ` Hugh Dickins
2008-06-03 1:19 ` Andrew Morton
2008-06-09 16:32 ` Ingo Molnar
2008-06-10 12:42 ` Hugh Dickins
2008-05-30 22:34 ` Jochen Voß
2008-05-30 22:36 ` Arjan van de Ven
2008-06-02 0:02 ` James Morris
2008-06-02 2:27 ` Arjan van de Ven
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=484080EC.9090707@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hugh@veritas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.