From: Michael Shuey <shuey@fmepnet.org>
To: Jacek Radajewski <jacek@usq.edu.au>
Cc: linux-poweredge@dell.com, linux-kernel@vger.kernel.org
Subject: Re: 2650 - tg3 on 2.4.18-19.7.xsmp rh7.3 ... OOPS YET AGAIN
Date: Thu, 23 Jan 2003 07:57:48 -0500 [thread overview]
Message-ID: <20030123125748.GB3285@lucky> (raw)
In-Reply-To: <08D7835AE15D6F4BABB5C46427F018DF0E608E@babbage.usq.edu.au>
On Thu, Jan 23, 2003 at 09:27:40AM +1000, Jacek Radajewski wrote:
> is the network card really the problem ? I don't want to be replacing all my network cards if the problem is elsewhere .... if you can understand the oops message please, please, please let me know where the problem is ...
You get oops messages? You're lucky - our PE 2650s would just lock up solid.
No oops message, no crash dumps (if we used a kernel with that patch), no
console messages, nothing. It would happen every 4-6 hours (and much sooner
when we tried a production-level amount of IO to the machine). At the time
we were using 2.4.18-18.7.x from RedHat 7.3.
Not sure if it was the network card (tg3) or the RAID adapter (aacraid). We
switched to 2.4.20, built with the same options (well, all that apply at any
rate) as the RedHat kernel. We haven't had a single problem since. You might
want to give that a try before replacing a pile of gigabit NICs....
--
Mike Shuey
next prev parent reply other threads:[~2003-01-23 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 23:27 2650 - tg3 on 2.4.18-19.7.xsmp rh7.3 ... OOPS YET AGAIN Jacek Radajewski
2003-01-22 23:53 ` jason andrade
2003-01-23 12:26 ` Mikael Pettersson
2003-01-24 6:12 ` GrandMasterLee
2003-01-23 2:19 ` Jeff Garzik
2003-01-23 12:57 ` Michael Shuey [this message]
[not found] <mailman.1043278441.2751.linux-kernel2news@redhat.com>
2003-01-23 0:19 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2003-01-23 2:02 Jacek Radajewski
2003-01-23 3:41 Gabriel Rosenkoetter
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=20030123125748.GB3285@lucky \
--to=shuey@fmepnet.org \
--cc=jacek@usq.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-poweredge@dell.com \
--cc=shuey@purdue.edu \
/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