Red Hat Bugzilla – Bug 436583
network interface fails with 18.104.22.168-12.fc8
Last modified: 2008-08-02 19:40:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20080208 Fedora/126.96.36.199-1.fc8 Firefox/188.8.131.52
Description of problem:
Motherboard has two network interfaces on board. Both will NOT enable with this kernel. Not able to manually turn on either.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot to latest kernel
2.network interface cards are turned off
Not able to get to the internet or my own network. Interface cards are disabled.
Not able to turn on via network setup.
Should have been able to get to internet and internal network.
Error message - Network not accessible.
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 2600+
stepping : 1
cpu MHz : 2079.583
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts
bogomips : 4161.06
clflush size : 32
desc: "3Com Corporation 3C920B-EMB Integrated Fast Ethernet Controller [Tornado]"
desc: "nVidia Corporation nForce2 Ethernet Controller"
There were a ton of network changes done in the build after yours. Could you
try the kernel from http://koji.fedoraproject.org/koji/buildinfo?buildID=42024
and see how that goes?
if it still fails, can you attach the dmesg from the failing kernel please.
Same problem here with same hardware by the looks of it. I will attach some
details and give referenced kernel a try.
Created attachment 297309 [details]
lspci and ifconfig of configuration under working kernel 184.108.40.206-137.fc8
Created attachment 297310 [details]
dmesg of kernel 220.127.116.11-22.fc8
Kernel 18.104.22.168-22.fc8.i686 from link in Comment #1 does not help. Attached is
dmesg output while booting that kernel.
Created attachment 297311 [details]
dmesg of working kernel 22.214.171.124-137.fc8
Attached is the dmesg of the working kernel 126.96.36.199-137.fc8 for reference.
Created attachment 297318 [details]
From kernel 2.6.24-22.fc8.i686
Do the addresses in the original /etc/sysconfig/network/devices/* match the ones
From the working kernel boot messages;
net eth1: device_rename: sysfs_create_symlink failed (-17)
udev: renamed network interface eth0 to eth1
It looks like the rename of the 3com 3c920 device wasn't working in 2.6.23 and
now it is.
A few months ago the other network card on this board started forgetting int MAC
and that was causing the ethx device to just start incrementing on every reboot
so I caught it at eth50-ish and disabled it and used the one that appeared to be
working. I thought (with some queries to the mailing list) that it was a
hardware failure at the time. I will re-enable it and go back and try to start
from square one with my network set up to see if everything is back to normal as
this might be related. I'll let you know what progress I have.
Cleared out the ethx.bak cruft in system-config-network and I reenabled the
other ethernet card in my bios so that it shows up. Now things seem to be
working fine. There still appears to be some persistent cruft showing up in
system-config-network eventhough I delete it and save after. I will have to go
into the /etc/ directory with a weed-wacker. See attached dmesg and screenshots
Created attachment 297760 [details]
dmesg of kernel 188.8.131.52-22.fc8 after 2nd network card enable and cruft removal
Created attachment 297761 [details]
Screenshot of network device cruft
Created attachment 297763 [details]
Screenshot of network hardware cruft
*** Bug 437698 has been marked as a duplicate of this bug. ***
kernel-184.108.40.206-50.fc8 has been submitted as an update for Fedora 8
kernel-220.127.116.11-50.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-2630
The new kernel -50 did not fix the problem.
kernel-18.104.22.168-50.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
With an IBM thinkpad X30 (which works with kernel 22.214.171.124-137.fc8 but no
2.6.24 version yet) kernel 126.96.36.199-50.fc8 still prevents the e100 ethernet card
(and the soundcard) from working. I'll attach a dmesg output with debug on the
Created attachment 299389 [details]
dmesg output for failing kernel
I don't think the IRQ 5 traceback in this dmesg is relevant -- I sometimes get
the "nobody cared" message for IRQ 5 even with 188.8.131.52-137.fc8
Created attachment 301393 [details]
Network Config showing continually incrementing device name on unused card
While networking is working for me now after manually clearing all my old
network devices out and letting Fedora reestablish them, clearly there is
something still going on. I believe that this latest fix may correct one bug
but there are more issues with this network driver on this mobo. The problems
for me started about a week or two before 2007-11-19 so I turned one NIC off in
the BIOS and ignored the issue. I reenabled it recently to see if things were
better. They are not as seen by the continual marching up of the device name
Created attachment 301394 [details]
A screenshot of a strange duplicate NIC showing up in my hardware list