From: Manfred Spraul <manfred@colorfullife.com>
To: Rob Leathley <mail@robleathley.uklinux.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: page_alloc 2.4.1 kernel BUG running java 1.3.0
Date: Sun, 18 Feb 2001 20:09:41 +0100 [thread overview]
Message-ID: <3A901DF5.6198F31F@colorfullife.com> (raw)
In-Reply-To: <3A9011E1.8A122306@robleathley.uklinux.net>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Rob Leathley wrote:
>
> [X] I have been suffering a lot of memory paging related Oops' on the
> above PC since upgrading to the 2.2.16 kernel. Most of these problems
> are fixed in 2.4.1 appart from the above. These problems don't appear
> on a faster machine (e.g. P3 733MHz) so could be related to race
> conditions? I appreciate that there is probably a bug in java 1.3.0 but
> it would be nice if it didn't kill the whole machine!
>
It's not a bug in java 1.3.0, that certain.
It's either a kernel bug or bad memory. Usually I'd say bad memory, but
your report is the third or forth one with __free_pages_ok(), so I
suspect a kernel bug.
Could you apply the attached patch to your kernel and run it until it
crashes again?
--
Manfred
[-- Attachment #2: patch-tst --]
[-- Type: text/plain, Size: 556 bytes --]
--- linux.old/mm/page_alloc.c Sun Feb 18 20:06:11 2001
+++ linux/mm/page_alloc.c Sun Feb 18 20:05:59 2001
@@ -70,8 +70,15 @@
if (page->buffers)
BUG();
- if (page->mapping)
+ if (page->mapping) {
+ printk(KERN_EMERG "found bad mapping %lxh.\n",
+ (unsigned long)page->mapping);
+ printk(KERN_EMERG "page->mapping->nrpages: %d.\n",
+ (int)page->mapping->nrpages);
+ printk(KERN_EMERG "page->mapping->a_ops: [<%lxh>]\n",
+ (unsigned long)page->mapping->a_ops);
BUG();
+ }
if (!VALID_PAGE(page))
BUG();
if (PageSwapCache(page))
prev parent reply other threads:[~2001-02-18 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 18:18 PROBLEM: page_alloc 2.4.1 kernel BUG running java 1.3.0 Rob Leathley
2001-02-18 19:09 ` Manfred Spraul [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=3A901DF5.6198F31F@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@robleathley.uklinux.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 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.