From: Jan Rychter <jan@rychter.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.26: kernel BUG at page_alloc.c:235\
Date: Tue, 13 Jul 2004 01:19:10 -0700 [thread overview]
Message-ID: <m2u0wcxqtd.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <20040712183819.GA5059@logos.cnet> (Marcelo Tosatti's message of "Mon, 12 Jul 2004 15:38:19 -0300")
>>>>> "Marcelo" == Marcelo Tosatti <marcelo.tosatti@cyclades.com> writes:
Marcelo> On Mon, Jul 12, 2004 at 11:31:49PM -0700, Jan Rychter wrote:
>> Linux 2.4.26 compiled with gcc-2.96 20000731 (RH7.1 2.96-85),
>> running on an Athlon XP2200+ clocked at 1800MHz.
>>
>> Any ideas?
Marcelo> Hi Jan,
Marcelo> The BUG() is at rmqueue(), "if (PageLRU(page)) BUG".
Marcelo> The same BUG has been seen before. The BUG means an LRU page
Marcelo> was found in a zone's free list (this is not a valid thing to
Marcelo> happen).
Marcelo> This could be either a driver bug (which uses a page after
Marcelo> freeing it, as wli smartly pointed out at the time) or faulty
Marcelo> hardware, as it showed to be in that occasion.
Marcelo> What drivers are you using
8139too for networking, reiserfs and ext2 for filesystems. Not much
more, really. IDE drives. iptable_nat + ip_conntrack. TUN/TAP. That's
pretty much it.
Marcelo> and, just as matter of "safety", have you ran memtest on this
Marcelo> box?
Unfortunately, no -- and it isn't all that easy for me to do so (the box
is remotely hosted). I will try to do it...
--J.
prev parent reply other threads:[~2004-07-12 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 6:31 2.4.26: kernel BUG at page_alloc.c:235 Jan Rychter
2004-07-12 18:38 ` 2.4.26: kernel BUG at page_alloc.c:235\ Marcelo Tosatti
2004-07-13 8:19 ` Jan Rychter [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=m2u0wcxqtd.fsf@tnuctip.rychter.com \
--to=jan@rychter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.