public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: gurudas pai <gurudas.pai@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] kernel BUG at arch/i386/mm/highmem.c:15!  on 2.6.23-rc8/rc9
Date: Thu, 4 Oct 2007 01:39:04 +1000	[thread overview]
Message-ID: <200710040139.04201.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <200710040053.19570.nickpiggin@yahoo.com.au>

On Thursday 04 October 2007 00:53, Nick Piggin wrote:
> On Thursday 04 October 2007 16:37, gurudas pai wrote:
> > Hi,
> >
> > While running Oracle database test on x86/6GB RAM machine panics with
> > following messages.
>
> Hi,
>
> Hmm, seems like something in sys_remap_file_pages might have broken.
> It's a bit hard to work out from the backtrace, though.
>
> Is it possible you can strace to find the arguments for the
> remap_file_pages that goes wrong?

Ahh, I think it's just underflowing the preempt count somewhere, which
is leading highmem.c:15 to just *think* it is in an interrupt.

But you aren't running a preemptible kernel, which makes it unusual...
it would have to be coming from interrupt code (or just random corruption).
Still, preempt debugging should catch those cases as well.

So, can you disregard my last message, and instead compile a kernel
with CONFIG_PREEMPT and CONFIG_DEBUG_PREEMPT, and see what
messages come up?

Thanks,
Nick

  reply	other threads:[~2007-10-04  8:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  6:37 [BUG] kernel BUG at arch/i386/mm/highmem.c:15! on 2.6.23-rc8/rc9 gurudas pai
2007-10-03 14:53 ` Nick Piggin
2007-10-03 15:39   ` Nick Piggin [this message]
2007-10-04 10:02     ` gurudas pai
2007-10-04 15:56       ` Hugh Dickins
2007-10-04 16:38         ` Linus Torvalds
2007-10-04 16:53           ` Hugh Dickins
2007-10-05  2:49         ` gurudas pai
2007-10-05  3:54           ` gurudas pai
2007-10-05 10:26             ` 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=200710040139.04201.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=gurudas.pai@oracle.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