From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Elikster <elik@webspires.com>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Oops - 2.4.24 Kernel
Date: Thu, 19 Feb 2004 17:54:58 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.58L.0402191753050.7378@logos.cnet> (raw)
In-Reply-To: <1514338595.20040219112756@webspires.com>
On Thu, 19 Feb 2004, Elikster wrote:
> Hello linux,
>
> I been getting those Oops of late that seems to have started nearly a
> month ago and been persisting thoughout, dispite changing the kernels
> few times to try and shake this out. Could this be the results of bad
> memory modules?
Yes this looks like bad hardware.
Verify the memory with memtest86.
> swap_free: Bad swap offset entry 3d000000
> kernel: kernel BUG at page_alloc.c:124!
prev parent reply other threads:[~2004-02-19 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 18:27 Elikster
2004-02-19 20:54 ` Marcelo Tosatti [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=Pine.LNX.4.58L.0402191753050.7378@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=elik@webspires.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
all inboxes | Powered by JetHome®