[Bug 609362] New: AMD SB 5785 NIC cannot work using tg3 module
http://bugzilla.novell.com/show_bug.cgi?id=609362 http://bugzilla.novell.com/show_bug.cgi?id=609362#c0 Summary: AMD SB 5785 NIC cannot work using tg3 module Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 7 Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: arindam.nath@amd.com QAContact: qa@suse.de CC: joachim.deguara@amd.com, henry.su@amd.com, shane.huang@amd.com, mchan@broadcom.com, boris.ostrovsky@amd.com Depends on: 580780 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #599130 +++ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 After default installation of openSuSE11.3 Milestone7, we cannot find 5785 NIC interface in the "ifconfig -a" listing. The dmesg says "No PHY devices" for this NIC. Reproducible: Always Steps to Reproduce: 1. Default install openSuSE11.3 Milestone7 32-bit/64-bit on AMD SB800/Hudson platforms. 2. Boot into OS, and list network interfaces using "ifconfig -a". 3. The 5785 NIC with MAC address 00:10:18:00:00:00 is not listed in the output of the above command. 4. Check dmesg, it says "eth%d: No PHY devices". Actual Results: Since the 5785 PHY cannot be probed by tg3 module, AMD internal NIC doesn't work with tg3 module alone. Expected Results: The support for 5785 PHY BCM50610 is provided by broadcom module. So the broadcom module should be loaded before tg3 module for the NIC to work. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c1
--- Comment #1 from Arindam Nath
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c2
Brandon Philips
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c3
--- Comment #3 from Brandon Philips
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c4
Arindam Nath
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c5
Brandon Philips
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c6
Arindam Nath
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c7
Brandon Philips
Our QA has confirmed that the kernel RPM provided above fixes the issue.
OK, I added it to our Kernel tree for openSUSE 11.3.
But we see another issue related to dynamic IP assignment. According to /etc/sysconfig/network/config file, by default NetControl is enabled. which takes care of network setup. But once the IP address is assigned to an interface, and then if we plug out the network cable, the IP address isn't detached from that interface.
This creates problem when we again plug in the cable back. We have worked-around it temporarily using NETWORKMANAGER=yes in the config file. Is this really a BUG?
NetControl doesn't monitor the link status like NetworkManager. If you need a new IP you need to: $ ifrenew eth0 So, I don't think it is a bug. If you don't agree please file a bug against yast. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=609362
http://bugzilla.novell.com/show_bug.cgi?id=609362#c8
Thomas Renninger
participants (1)
-
bugzilla_noreply@novell.com