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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:01:02 EST