Red Hat Bugzilla – Bug 170887
Neterion(S2io) adapter not functional after running offline diagnostics
Last modified: 2007-11-30 17:07:21 EST
Description of problem:
After offline diagnostics(ethtool -t) is run on the Neterion(S2io) adapter,
the NIC is not functional.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 120009 [details]
Fix for offline diag problem mentioned in bug and related fixes.
This patch contains the following fixes :
1. Adapter is now functional after running offline diagnostics.
2. Added SPI interface code(for Xframe II) to perform EEPROM read/write
3. Modify expected value in register test depending on adapter(Xframe I/II).
4. Correct return values for functions called from offline diag routine.
5. Use correct API to write to RLDRAM registers.
As Bugzilla is not an official support channel, has no response guarantees, and
may not route your issue to the correct area to assist you, you might wish to
file a support request. To do this, please either contact Red Hat's Technical
Support line at 888-GO-REDHAT or file a web ticket at
http://www.redhat.com/apps/support/. Using the official support channels above
will guarantee that your issue is handled appropriately and routed to the
individual or group which can best assist you with this issue and will also
allow Red Hat to track the issue, ensuring that any applicable bug fix is
included in all releases and is not dropped from a future update or major
Has this patch gone upstream? If not, when can I expect to see it there?
The patch is not yet submitted to open source kernel. I plan to do it today
(worst case tomorrow).
Test kernels w/ the above patch available here:
Please verify that they behave as expected, and post the results
Verified that the test kernel works fine.
Also, the patch has been accepted into upstream by open source community.
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 the 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.