From: Hugh Dickins <hugh@veritas.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25.6 kernel BUG at mm/highmem.c:319!
Date: Thu, 26 Jun 2008 18:13:02 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0806261756160.32336@blonde.site> (raw)
In-Reply-To: <20080626083749.4fd0b403@infradead.org>
On Thu, 26 Jun 2008, Arjan van de Ven wrote:
> On Thu, 26 Jun 2008 10:59:42 -0400
> Dave Jones <davej@redhat.com> wrote:
>
> > Anyone know how this can happen ?
> > We just got a report from a user who is hitting the
> >
> > BUG_ON(!PageHighMem(page));
> >
> > in set_page_address().
>
> we discussed this 2 or 3 weeks ago as part of the kerneloops reports...
> everyone is puzzled... it's the number 20 report right now.
>
> http://www.kerneloops.org/search.php?search=set_page_address
>
> it seems that fuse is a very popular module when this hits...
I'm as puzzled now as back then. And fuse isn't in Dave's list.
But I did notice after reporting back on it, that i915 appears in all
of the reports I looked at; and Fedora does have some drm/i915
patches, which do involve kmap.
I know precious little about drm, but didn't spot anything in those
patches which was likely to cause this: they might be a good place
for Dave to start looking though.
If this user is suffering from it repeatedly, might s/he be prepared
to run a kernel with more debug in it? Though at this moment,
I don't know what it is that I'd like to be looking for anyway -
it's always easier to come up with debug patches when you've a
hypothesis as to what's going on, which I don't have.
Hugh
prev parent reply other threads:[~2008-06-26 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 14:59 Dave Jones
2008-06-26 15:37 ` Arjan van de Ven
2008-06-26 17:13 ` Hugh Dickins [this message]
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.0806261756160.32336@blonde.site \
--to=hugh@veritas.com \
--cc=arjan@infradead.org \
--cc=davej@redhat.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
all inboxes | Powered by JetHome®