mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adam J. Richter" <adam@yggdrasil.com>
To: tmolina@cox.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.5.40 64GB highmem BUG()
Date: Mon, 7 Oct 2002 18:12:01 -0700	[thread overview]
Message-ID: <200210080112.SAA01553@adam.yggdrasil.com> (raw)

On 2002-10-08 0:48:32, Thomas Molina wrote:
>On Mon, 7 Oct 2002, Adam J. Richter wrote:
>
>>       Although 2.5.40 has been out for a while, I think I ought
>> to post this bug as I haven't seen any other mention of it.
>> 
>>       When I boot an 2.5.40 x86 kernel built with CONFIG_HIGHMEM64G,
>> and with a 920kB initial ramdisk (2.2MB uncompressed), I get a kernel
>> BUG() at highmem.c line 480, preceded by a message saying "scheduling
>> with KM_TYPE 15 held!"  The machine on which I experienced this
>> problem has 1.25GB of RAM.  The problem occurs with and without
>> CONFIG_PREEMPT.  All kernels that tried were SMP kernels running on a
>> uniprocessor.
>> 
>>       The problem does not occur if I build 2.5.40 with
>> CONFIG_HIGHMEM4G or CONFIG_NOHIGMEM.  So, it's probably not causing
>> problems for many people, but I thought I should report it anyhow.
>
>Does the accompanying trace output say BUG(), or is there a might_sleep() 
>in the trace output?  In other words, is it a scheduling while holding a 
>lock kind of thing?

	It is the BUG() statement in check_highmem_ptes in mm/highmem.c:

#if CONFIG_DEBUG_HIGHMEM
void check_highmem_ptes(void)
{
        int idx, type;

        preempt_disable();
        for (type = 0; type < KM_TYPE_NR; type++) {
                idx = type + KM_TYPE_NR*smp_processor_id();
                if (!pte_none(*(kmap_pte-idx))) {
                        printk("scheduling with KM_TYPE %d held!\n", type);
                        BUG();
                }
        }
        preempt_enable();
}
#endif

	I'm updating to 2.5.41 and will post a trace if the problem
still occurs.

Adam J. Richter     __     ______________   575 Oroville Road
adam@yggdrasil.com     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America
                         "Free Software For The Rest Of Us."

             reply	other threads:[~2002-10-08  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08  1:12 Adam J. Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-21  9:43 Adam J. Richter
2002-12-21  9:48 ` William Lee Irwin III
2002-10-07 13:27 Adam J. Richter
2002-10-08  0:48 ` Thomas Molina
2002-12-19 23:36 ` William Lee Irwin III

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=200210080112.SAA01553@adam.yggdrasil.com \
    --to=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cox.net \
    /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®