Bug 748973

Summary: f15 sundance pci ethernet [13f0:0200] module crashes when plugged to gigabit router (works with 10/100 but not 1000)
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-11 17:51:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
messages, nic problem none

Description Reartes Guillermo 2011-10-25 18:05:34 UTC
Created attachment 530149 [details]
messages, nic problem

Description of problem: 

I brought a new router (gigabit) some days ago.
When i attached that nic to tha gigabit router, the kernel sundande driver complained about the transmit queue and then it went to sleep... 

The nic is a 10/100 card, but it seems to not to be able to obtain/mantain 100 mpbs speed with that router. Previously i worked ok. Tried another cable, no luck. It works with the old router, though...

01:08.0 Ethernet controller [0200]: Sundance Technology Inc / IC Plus Corp IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY [13f0:0200] (rev 31)

I still have the nic, in case that is caused by a real software bug, i may be able to retest with that nic.


Version-Release number of selected component (if applicable):

kernel 2.6.40.6-0.fc15.x86_64

How reproducible: allways.

Steps to Reproduce:
1. plug the sundance nic to a linksys wrt320N
2. no net
3. no net
  
Actual results:
no ethernet device or no ip connectivity

Expected results:
100 mpbs speed link and tcp/ip connectivity

Additional info:
I replaced the card to another (different chipset) to use the new network hw.

static ip is used, no NM is running.

-------------

Examples:

eth0 : reset not completed !!
kernel: [ 8381.675052] eth0: Link down
kernel: [ 8381.675052] eth0: Something Wicked happened! ffff.
kernel: [ 8381.700117] eth0: Link down
kernel: [ 8381.712320] br0: port 1(eth0) entering forwarding state
kernel: [ 8397.141808] eth0: Link up
kernel: [ 8397.142095] eth0: Link changed: 100Mbps, full duplex
kernel: [ 8397.145384] br0: port 1(eth0) entering forwarding state
kernel: [ 8397.145395] br0: port 1(eth0) entering forwarding state
kernel: [ 8406.361728] eth0: Link down
kernel: [ 8406.373209] br0: port 1(eth0) entering forwarding state
kernel: [ 8493.273295] eth0 : reset not completed !!


kernel: [ 8533.712065] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf0/0x150()
kernel: [ 8533.712072] Hardware name: System Product Name
kernel: [ 8533.712079] NETDEV WATCHDOG: eth0 (sundance): transmit queue 0 timed out
kernel: [ 8533.712497] eth0: Transmit timed out, TxStatus ff TxFrameId ff, resetting...

Comment 1 Josh Boyer 2012-06-07 15:06:32 UTC
Are you still seeing this with 2.6.43/3.3?

Comment 2 Josh Boyer 2012-07-11 17:51:25 UTC
Fedora 15 has reached it's end of life as of June 26, 2012.  As a result, we will not be fixing any remaining bugs found in Fedora 15.

In the event that you have upgraded to a newer release and the bug you reported is still present, please reopen the bug and set the version field to the newest release you have encountered the issue with.  Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered.

Thank you for taking the time to file a report.  We hope newer versions of Fedora suit your needs.