[3105] in Release_7.7_team
Re: Case 254686: Poor GX150 performance revisited.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Fri Jan 25 12:41:37 2002
Message-ID: <QwINXCBz0001RQyZtJ@mit.edu>
Date: Fri, 25 Jan 2002 17:41:34 +0000 ()
From: Bill Cattey <wdc@MIT.EDU>
To: Matt Braun <matt@MIT.EDU>
CC: release-team@MIT.EDU, net-help@MIT.EDU, amb@MIT.EDU, ops@MIT.EDU
In-Reply-To: <200201251340.IAA27624@forever.mit.edu>
Excerpts from mail: 25-Jan-102 Re: Poor GX150 performance .. Matt
Braun@MIT.EDU (189)
> Just for my information here, do you have more specifics about whihc
> GX150's have this problem? And is there a way to check with version of
> the chip set a given device has?
Yes.
If you look in /mit/wdc/3com you will find the vortex-diag program among
others. Becker used the Manufacture date output to assert:
Excerpts from pm.linux: 10-Jan-102 Re: [3c509] Question about .. Donald
Becker@scyld.com (2422*)
> > Manufacture date (MM/DD/YYYY) 6/10/2000, division , product .
> Hmmm, this appears to be a rather old card -- produced just about the
> time when the first "Cx" chip was released.
> > MII PHY found at address 1, status 0024.
> > MII PHY found at address 2, status 0024.
> > MII PHY found at address 3, status 0024.
> > MII PHY found at address 4, status 0024.
> It really does appear to be an early "Cx" board, with bogus transceiver
> responses. Using an updated driver should work around the problem.
So I guess a definitive test would be:
Log onto a GX150 as root.
Run
vortex-diag -v
Look for manufacture dates around June 2000
-wdc
