Red Hat Bugzilla – Bug 524241
ethtool: typo in "speed 10000" command line parsing
Last modified: 2014-08-31 19:29:17 EDT
Description of problem:
It prevents setting speed to 10000 ... Here's the patch:
--- ethtool.c 2007-07-26 19:22:06.000000000 +0200
+++ ethtool.c.new 2009-09-18 10:33:17.841224000 +0200
@@ -524,7 +524,7 @@
speed_wanted = SPEED_1000;
else if (!strcmp(argp[i], "2500"))
speed_wanted = SPEED_2500;
- else if (!strcmp(argp, "10000"))
+ else if (!strcmp(argp[i], "10000"))
speed_wanted = SPEED_10000;
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. sudo ethtool -s eth1 speed 10000
print ethool usage
setting the iface speed to 10000
Also reported here: http://firstname.lastname@example.org/msg58263.html
The fix for this is included in the patch for #529395
*** Bug 484168 has been marked as a duplicate of this bug. ***
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~
RHEL 5.5 Beta has been released! There should be a fix present in this
release that addresses your request. Please test and report back results
here, by March 3rd 2010 (2010-03-03) or sooner.
Upon successful verification of this request, post your results and update
the Verified field in Bugzilla with the appropriate value.
If you encounter any issues while testing, please describe them and set
this bug into NEED_INFO. If you encounter new defects or have additional
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.
I guess I won't be able to test the fix:
"To access these Red Hat Network benefits, customers must log in to Red Hat Network using a Red Hat login associated with at least one active subscription to a Red Hat product or service."
Not my case, sorry, only CentOS here, and I'm not sure there's a CentOS 5.5 Beta out there ...
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.