Bug 155561

Summary:	Gigabit nic Marvell Yukon fails at GBit speed, no working network or super poor performance.
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	K. De Hoop <kdehoop>
Component:	Network	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium
Version:	unspecified
Target Milestone:	---
Hardware:	x86-64
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	dmesg output hwinfo network ifconfig output modules messages routing info messages whitout the mingetty error filling up the log

Description K. De Hoop 2006-03-06 20:37:31 UTC

I have a suse 10 64bit server connected to my workstation whit a corss-link cable. My workstation (windows xp sp2) has a d-link/intell Gbit nic, the server consists of a Asus AV8 whit a onboard Marvell Yucon Gbit nic. 

Using the network (samba, bittorrent, xmirc, firefox) whit a 2pair (cat5) cross-link cable gives 100% good, reliable 100mbit connection. Upgrading the cable to 4pair cat6 cross-link makes the server fail networking. 

The D-link/intell nic switches to Gbit speed, faster transfer is enabled. Copying files from samba over to my workstation gives a 14% network utilization (scale 1gbit) and 100% cpu load… PoorPoorPoor. 
The other way around doesn’t work, I cant copy files from my workstation to the server.

Starting my torrent client on the server fails, Azureus. The software failed network initialization whit some vague error. Vmware GXS can not bind to the vm nic failing all vm’s. Browsing the internet even fails now.

I rebooted a couple of time after changing the module sk98lin options to give the Mavell nic some instructions. Still no success. Upgrading the module whit the manufacture release was no success as well. I am running back on my old 2pair cross-cable at 100mbit till i find a solution.

Comment 1 K. De Hoop 2006-03-06 20:38:56 UTC

Posted on the forum as well.
http://forums.suselinuxsupport.de/index.php?showtopic=32033&st=0&gopid=150301&#entry150301

Comment 2 Michael Gross 2006-03-07 14:33:11 UTC

Please provide some more information. Are there any kernel messages, has the firewall influence on that, attach the output of `hwinfo --network', `ifconfig' (after some traffic) and `route -n' as well as 300 lines of your syslog and the output of `lsmod'.

Comment 3 Michael Gross 2006-03-15 14:04:16 UTC

Please reopen this report once you can provide more information.

Comment 4 K. De Hoop 2006-03-15 21:28:21 UTC

This weekend i provide more info, i was not able to respond earlier. Sry for the inconvenience

Comment 5 Michael Gross 2006-03-16 15:39:23 UTC

OK I'm waiting ;)

Comment 6 K. De Hoop 2006-03-19 18:19:10 UTC

Created attachment 73849 [details]
dmesg output

Comment 7 K. De Hoop 2006-03-19 18:21:24 UTC

Created attachment 73850 [details]
hwinfo network

Comment 8 K. De Hoop 2006-03-19 18:21:43 UTC

Created attachment 73851 [details]
ifconfig output

Comment 9 K. De Hoop 2006-03-19 18:21:56 UTC

Created attachment 73852 [details]
modules

Comment 10 K. De Hoop 2006-03-19 18:22:09 UTC

Created attachment 73853 [details]
messages

Comment 11 K. De Hoop 2006-03-19 18:22:28 UTC

Created attachment 73854 [details]
routing info

Comment 12 K. De Hoop 2006-03-19 18:26:13 UTC

If u plz, the information u asked for. Hope u guys can solve this problem. Greating!!

Comment 13 Michael Gross 2006-03-20 13:06:28 UTC

Reassigning to the kernel maintainers.

Comment 14 K. De Hoop 2006-03-21 13:01:57 UTC

Created attachment 74171 [details]
messages whitout the mingetty error filling up the log

Comment 15 Greg Kroah-Hartman 2006-03-23 06:33:13 UTC

Does this happen on the 10.1 beta release?

Comment 16 K. De Hoop 2006-03-23 14:48:16 UTC

Nope its open suse 10.0

Comment 17 Karsten Keil 2006-03-23 17:39:03 UTC

From your dmesg:
sk98lin: Network Device Driver v8.30.2.3
(C)Copyright 1999-2005 Marvell(R).
This is not the version from 10.0 so far I know.

What Greg want to ask is, please test with 10.1 Beta to see if this bug is fixed in the new versions.

Comment 18 K. De Hoop 2006-03-24 08:10:16 UTC

Like stated on the forum (the link is posted above) i have installed the newest manufacture driver. Regarding the question, how will i test whit 10.1 beta? I don’t have spare hardware and I am certainly not going tot reinstall my server. So far Greg answer (if that is what he wants)  sounds like a microsoft solution "please apply SPxx, add more ram, upgrade and pay us”. So plz reconsider the above stated answer in order to solve this bug.

Comment 19 Karsten Keil 2006-03-24 12:08:57 UTC

Sorry we cannot fix this problem in the sk98lin driver, we do not have any hardware specs or development agreements with Marvell.
Only the manufacturer (Marvell) can fix it. Since you already tried their latest driver and the problem still exist, you should contact them.
Since it was known to the community, that the Marvell drivers have problems and Marvell failed to keep the sk98lin driver uptodate, a independ driver development was started by ODSL people (sky2), so a patched sk98lin will be not longer on our distribution.