[3201] in Release_7.7_team
Re: some GX150 NIC's may have been stopped completely by the recent
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Mar 27 00:38:06 2002
From: Bill Cattey <wdc@MIT.EDU>
To: Alex Coventry <alex_c@mit.edu>
Cc: hotline@mit.edu, release-team@mit.edu
In-Reply-To: <200203270514.AAA22255@m2-225-7.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 27 Mar 2002 00:38:03 -0500
Message-Id: <1017207483.5247.307.camel@tokata.mit.edu>
Mime-Version: 1.0
On Wed, 2002-03-27 at 00:14, Alex Coventry wrote:
>
> hi. m2-225-{1,3,8} had no network this evening. booting m2-225-8
> single user mode, i could run "ifup eth0" without errors, but also
> without achieving any connectivity. i was a little anxious to get a
> backup off m2-225-8, so i played around with it a bit. several
> invocations of the mii-diag commands described on release-team failed to
> bring it back. i was still hoping it was a firmware issue, so i tried
> booting it from a stock redhat 7.1 install image, bringing it up on the
> net as if i were going to do a net install, and then rebooting. this
> worked, although the resulting bandwidth was very low, starting around
> 10kb/s and dropping to about 1kb/s before i gave up on it.
>
> the same trick brought m2-225-3's nic back from the dead. i've left
> m2-225-1 alone, in case anyone wants to have a look at the broken state.
> i went by sipb later, and noticed that w20-575-2 was also off the net.
> it may have the same problem.
>
> hth.
> alex.
People who find problematic systems running 9.0.25, and who use
vortex-diag to poke at them:
Please send me email with the output of
vortex-diag -eav
before AND after you try stuff.
I'll be able to get a much clearer sense of what's going on that way.
-wdc
