Red Hat Bugzilla – Bug 108473
3c59x + kudzu == boom
Last modified: 2013-07-02 22:16:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2)
Description of problem:
If the 3c59x module is loaded, but no communication is attemped, it appears
fine. Once communication is attempted, it never actually succeeds, and the
console fills up with messages about dirty registers.
I'll attach a sample from messages.
here's the beginning of the message:
Flags; bus-master 1, dirty 1(1) current 1(1)
Transmit list 00000000 vs. c3f71240.
0: @c3f71200 length 8000002a status 8000002a
1: @c3f71240 length 00000000 status 00000000
2: @c3f71280 length 00000000 status 00000000
3: @c3f712c0 length 00000000 status 00000000
BTW, the fibre version of the card appears to work flawlessly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install a 3c905TX
2. attempt communication
Actual Results: no communication succeeds, cryptic messages on the console
Expected Results: should be able to communicate flawlessly.
I'll attach the relevant lines from messages.
The hardware that it's been tried on are:
Asus A7N8X and
The 3com cards are known to be fine, worked with WS 2.1 and currently work with
Created attachment 95591 [details]
relevant entries from /var/log/messages
See bug #102685!
It is known since 2003-08-19.
An attention: you can only reproduce this bug with the Boomerang card!
Turn Kudzu off at runlevel boot with chkconfig --level 345 off. Then
reboot and the nic should work. Let me know if that works. Thanks
Appears to be working beautifully.
*** Bug 108465 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 107389 ***
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.