public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Flory <sflory@rackable.com>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: Tyan i7501 Pro (S2721-533) lock-up (e1000?)
Date: Tue, 30 Sep 2003 10:36:58 -0700	[thread overview]
Message-ID: <3F79BF3A.90208@rackable.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0309301059350.13584-100000@sweetums.bluetronic.net>

Ricky Beam wrote:
> On Mon, 29 Sep 2003, Samuel Flory wrote:
> 
>>>Anyone else seeing similar problems with the i7501 pro?
>>
>>  We been using a lot of 2721-533 without issues.  Are you certain it's
>>networking?  Have you tried a mem tester like memtst86 or ctcs?  Does
>>the issue occur with addon cards, or the e100 nic?
> 
> 
> And I've used it's 603 cousins as well without issue.  I was thinking
> after I sent the message APPro may be using uncertified memory, however,
> I don't want to have to pull it back out of the rack to find out.
> (Personally, I'd rather build them myself than buy them pre-assembled.)
> 
> It works fine until a large volume of traffic is sent at it on the gig
> ports.  It works sometimes, and locks up other times.  On rare occasions,
> the kernel stops receiving traffic -- the lights are blinking and the chip
> counters are still going up, but no traffic is showing up. (ethtool -r
> gets us back going.)

   So what is the difference when you query the interface with ethtool 
in the good vs bad state?  What does the switch think the port is set to 
in the good state vs the bad?  What sort of switch are you using?

> 
> It's currently been running for 16 hours.  I made a few changes to BIOS
> settings (nothing that should matter.)  One thing I've noticed, even though
> Tyan only has ONE BIOS published for the board, both of the boards here
> have different versions (between themselves and what tyan is pushing.)
> 

   Tyan tends to produce custom bios revs for various customer 
requirements, or to fix bugs found by that customer.  It often takes a 
while for these things to hit the main bios.


> I'm preparing to slam it with 87Mbps of traffic (as fast as I can transmit
> without error) and see how long it lasts.


   It's also possible that the mother board is defective in some manner.

> 
> --Ricky
> 
> PS: There's a Del 2650 right below it.  There are reports of problems with
> the e1000's in that thing.  It's the same chipset as I recall.
> 

   I wouldn't know about that;-)


-- 
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>


      reply	other threads:[~2003-09-30 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 22:37 Tyan i7501 Pro (S2721-533) lock-up (e1000?) Ricky Beam
2003-09-30  1:51 ` Samuel Flory
2003-09-30 15:13   ` Ricky Beam
2003-09-30 17:36     ` Samuel Flory [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=3F79BF3A.90208@rackable.com \
    --to=sflory@rackable.com \
    --cc=jfbeam@bluetronic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox