From: ChristopherHuhn <c.huhn@gsi.de>
To: linux-kernel@vger.kernel.org
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>, Walter Schoen <w.schoen@GSI.de>
Subject: Re: Kernel Bug at spinlock.h ?!
Date: Mon, 03 Mar 2003 11:12:18 +0100 [thread overview]
Message-ID: <3E632A82.3090304@GSI.de> (raw)
In-Reply-To: Pine.LNX.4.50.0303030348130.25240-100000@montezuma.mastecende.com
Zwane Mwaikambo wrote:
>Sounds like possible memory corruption (can you vouch for the reliability
>of your RAM?)
>
The similar problem occurs on many of our machines, so I would exclude
memory corruption.
>Might be worthwhile posting the oops in it's entirety. Is
>EIP normally in __run_timers? Do you run a heavy networking load?
>
The numbers crunched by these machines are loaded from and writtem to
the net, so I would assume that.
We had these machines running potato with 2.2.21 since last summer and
the kernel never oopsed.
Due to this fact I expect this to be a bug in the SMP code of 2.4.20 or
a kernel misconfiguration by us.
I'll send the next oops as soon as it occurs.
Kind regards,
Christopher
next prev parent reply other threads:[~2003-03-03 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 8:11 Kernel Bug at spinlock.h ?! ChristopherHuhn
2003-03-03 8:51 ` Zwane Mwaikambo
2003-03-03 10:12 ` ChristopherHuhn [this message]
2003-03-03 15:13 ` ChristopherHuhn
2003-03-03 15:30 ` Tomas Szepe
2003-03-03 15:41 ` Richard B. Johnson
2003-03-03 16:03 ` ChristopherHuhn
2003-03-03 16:42 ` Richard B. Johnson
2003-03-03 17:49 ` Zwane Mwaikambo
2003-03-03 17:49 ` Zwane Mwaikambo
2003-03-04 13:58 ` ChristopherHuhn
2003-03-05 5:49 ` Zwane Mwaikambo
2003-03-05 5:49 ` Zwane Mwaikambo
2003-03-06 13:16 ` ChristopherHuhn
2003-03-07 15:47 ` Zwane Mwaikambo
2003-03-07 15:47 ` Zwane Mwaikambo
2003-03-10 8:52 ` ChristopherHuhn
2003-03-03 16:39 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 10:32 ChristopherHuhn
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=3E632A82.3090304@GSI.de \
--to=c.huhn@gsi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=w.schoen@GSI.de \
--cc=zwane@linuxpower.ca \
/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.