[3210] in Release_7.7_team
Re: Progress on 3com bug!
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Fri Mar 29 01:54:20 2002
Date: Fri, 29 Mar 2002 01:52:03 -0500
Message-Id: <200203290652.BAA01193@w20-575-8.mit.edu>
From: Garry Zacheiss <zacheiss@MIT.EDU>
To: Bill Cattey <wdc@mit.edu>
CC: release-team@mit.edu, ops@mit.edu, hotline@mit.edu, alex_c@mit.edu,
csnowden@mit.edu
In-reply-to: "[3209] in Release_7.7_team"
I decided to independantly verify your findings. What I observed
agrees with you; here's a more detailed breakdown.
All my testing was done on a machine in the "slow" state, as I
had fixed all the "no network" machines in w20 last night.
What I observed was:
- rebooting the machine without running any commands: still
slow.
- running only mii-tool -R and rebooting: still slow.
- running only vortex-diag -x 2 -w and rebooting: no
network.
- running both vortex-diag -x 2 -w and mii-tool -R and
rebooting: networking works normally.
I also observed that the vortex-diag and mii-tool commands being
seperated by a reboot doesn't seem to have any impact; running mii-tool
-R from a machine whose network you had just killed by running
vortex-diag and rebooting wil recover with full network speed on the
next reboot.
So it sounds like the procedure you describe, and the patch Greg
submitted to source-reviewers to incorporate it into the 9.0.26
athena-ws spec file, are the correct approach.
Garry
