Comment on attachment 174241[details]
/var/log/messages excerpts corresponding to successful boot with non-smp kernel using tg3 v.3.52RH driver
For anyone who is uncomfortable with the hostname change from "localhost" to
"dev08" above, I've created an attachment corresponding to a successful boot
with the non-smp kernel 2.4.21-50.EL of RHEL 3 U9 using tg3 driver version
3.52RH. The result appears to be the same (ifup succeeds and still there's an
IRQ routing conflict.)

Hmmm, this is curious. Are you running with hyper-threaded processors by any
chance? What if you boot the smp kernel (with the RH-supplied tg3 driver) and
use the 'noht' kernel command line option. The smp kernel definitely seems to
behave in an interesting way on this system, so I'd like to drop hyper-threading
out of the picture.

In comment #7 and comment #8 above I've attached /var/log/message outputs that
correspond to booting the RHEL3 U9 smp kernel with the 'noht' kernel boot option.
In both cases, the behavior seemed the same as described in comment #4 above,
namely that DHCP did not work upon bootup and static assignment was possible
(e.g., 'ifconfig eth0 192.168.1.71 up').
However, as described in comment #4, when I would ping another computer on the
network, the responses seemed to queue rather than print to the console. One
modification I would make to comment #4 is that it appears as though one can
effect the ping responses printing to the console by hitting any key, not
necessarily just the <ctrl><c> combination.
[comments #9 and #10 are duplicates of #7 and #8 and can be deleted - sorry.]

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:
http://www.redhat.com/security/updates/errata/
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.

Note

You need to
log in
before you can comment on or make changes to this bug.