From: Tim Moore <linux-kernel@nsr500.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.26 oops
Date: Wed, 21 Jul 2004 14:52:02 -0700 [thread overview]
Message-ID: <40FEE582.9020200@nsr500.net> (raw)
In-Reply-To: <20040721145900.9878.69804.Mailman@linux.us.dell.com>
Peter Santoro wrote:
> H/W: asus p3b-f, 1GB ecc ram, 1.4 Ghz tualatin celeron (no overclocking)
What slocket are you using? Is it set to "auto"?
What are the CPU/FSB/PCIbus/memory BIOS settings?
Have you tried recompiling with CONFIG_M686=y?
Have you tried turning ECC off?
Are you paging a lot or running out of swap?
t.
> S/W: slackware 9.1 with updates, kernel 2.4.26
>
> System was running fine for almost 4 years (originally was P3 600E,
> upgraded to tualatin 1+ yr ago). Prior to getting these 2.4.26 oops, I
> got random 2.4.26 lockups and reboots (usually using mouse in X) with
> nothing on my screen or in my logs. I decided to install a new Antec
> Truepower 430W psu, but the problems remained. Antec tech support told
> me that my new psu was not within spec, so they replaced it. I'm now
> running with the replaced Antec Truepower 430 psu and getting a 2.4.26
> oops (usually happens when selecting a newsgroup via mouse in mozilla
> 1.7). I suppose I could have a H/W problem, but just in case it's a
> valid kernel problem, I'm submitting this email.
>
> Any help is appreciated.
>
>
> Thank you,
>
>
> Peter Santoro
>
> =============== FROM SYSLOG ============
>
> ksymoops 2.4.9 on i686 2.4.26. Options used
> -v /usr/src/linux/vmlinux (specified)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.26/ (default)
> -m /usr/src/linux/System.map (default)
>
> kernel BUG at page_alloc.c:103!
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c0134346>] Not tainted
> ...
>
--
| for direct mail add "private_" in front of user name
next parent reply other threads:[~2004-07-21 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040721145900.9878.69804.Mailman@linux.us.dell.com>
2004-07-21 21:52 ` Tim Moore [this message]
2004-07-21 13:43 kernel 2.4.26 oops Peter Santoro
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=40FEE582.9020200@nsr500.net \
--to=linux-kernel@nsr500.net \
--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 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.