From: Jason Gauthier <jgauthier@lastar.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.7 SMP trouble?
Date: Mon, 19 Jul 2004 15:16:26 -0400 [thread overview]
Message-ID: <2873B794CB1BE04F80E2968B438680E503ACF5C1@server6.ctg.com> (raw)
I've found an IBM netfinity (5600) box that was shelved a few years ago. I
spent $80 and got two processors for it. (P3-667).
I put them in the box, installed Linux (slackware) and upgraded the kernel
to 2.6.7. I then started installing my software on it. Nagios, MRTG,
samba, and some other tools we use for network monitoring. This is going to
be an upgrade to a monitoring server we have. Well, I went home, came in
the next day and the box was locked hard. No messages, no console output.
Just dead.
Thinking it was a fluke, I fired it up. Again, after several hours running;
total death. So, I figured I have two options. Software or hardware is
making it die. I removed each processor in turn, and ran the box for over
24 hours under HIGH stress. (5+ load average). The system is running the
above mentioned software. But, just to make sure this processor gets a
workout I am compiling code over and over. Both processors have been rock
solid for the duration of the test.
I then placed both processors in the box and started the same test. It was
dead within 8 hours. I am now very suspicious of the kernel.
So, I installed 2.4.22 and ran the same tests. It went over 48 hours with
no issues. Now I'm certain it's the kernel. Can anyone confirm any SMP
issues that might cause this?
Thanks,
Jason
next reply other threads:[~2004-07-19 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 19:16 Jason Gauthier [this message]
2004-07-19 20:04 ` Richard B. Johnson
2004-07-20 14:22 ` Zwane Mwaikambo
2004-07-20 19:57 ` Bill Davidsen
2004-07-20 14:21 Jason Gauthier
2004-07-20 14:34 ` Zwane Mwaikambo
2004-08-02 13:14 Jason Gauthier
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=2873B794CB1BE04F80E2968B438680E503ACF5C1@server6.ctg.com \
--to=jgauthier@lastar.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®