Bug 11271 - BUG: fealnx in 2.6.27-rc1
BUG: fealnx in 2.6.27-rc1
Status: CLOSED UNREPRODUCIBLE
Product: Drivers
Classification: Unclassified
Component: Network
All Linux
: P1 normal
Assigned To: Jeff Garzik
:
Depends on:
Blocks: Regressions-2.6.26
  Show dependency treegraph
 
Reported: 2008-08-07 12:53 UTC by Rafael J. Wysocki
Modified: 2008-11-09 13:18 UTC (History)
0 users

See Also:
Kernel Version: 2.6.27-rc1
Tree: Mainline
Regression: Yes


Attachments
Commit 28cd4289abc2c8db90344ee4ff064a9bdf086fdf (2.79 KB, patch)
2008-09-16 12:20 UTC, Jeff Garzik
Details | Diff

Description Rafael J. Wysocki 2008-08-07 12:53:12 UTC
Subject    : BUG: fealnx in 2.6.27-rc1
Submitter  : "Jaswinder Singh" <jaswinderlinux@gmail.com>
Date       : 2008-08-05 14:58
References : http://marc.info/?l=linux-netdev&m=121794762016830&w=4

This entry is being used for tracking a regression from 2.6.26.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Rafael J. Wysocki 2008-08-10 05:52:18 UTC
On Sunday, 10 of August 2008, Jaswinder Singh wrote:
> Hello all,
> 
> On Sun, Aug 10, 2008 at 4:13 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=11271
> > Subject         : BUG: fealnx in 2.6.27-rc1
> > Submitter       : Jaswinder Singh <jaswinderlinux@gmail.com>
> > Date            : 2008-08-05 14:58 (5 days old)
> > References      : http://marc.info/?l=linux-netdev&m=121794762016830&w=4
> >
> >
> 
> This still exists on 2.6.27-rc2 when I transfer some data on RealTek 8139C NIC.
> 
> 01:00.0 Ethernet controller: MYSON Technology Inc SURECOM EP-320X-S
> 100/10M Ethernet PCI Adapter
> 	Subsystem: MYSON Technology Inc SURECOM EP-320X-S 100/10M Ethernet PCI Adapter
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> 	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> 	Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 64 bytes
> 	Interrupt: pin A routed to IRQ 21
> 	Region 0: I/O ports at d800 [size=256]
> 	Region 1: Memory at ff8ffc00 (32-bit, non-prefetchable) [size=1K]
> 	Expansion ROM at e6a00000 [disabled] [size=64K]
> 	Capabilities: [88] Power Management version 2
> 		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA PME(D0-,D1+,D2-,D3hot+,D3cold+)
> 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 	Kernel driver in use: fealnx

Comment 2 Rafael J. Wysocki 2008-08-11 04:39:02 UTC
Handled-By : Francois Romieu <romieu@fr.zoreil.com>
Comment 3 Rafael J. Wysocki 2008-08-11 04:40:01 UTC
References : http://lkml.org/lkml/2008/8/10/98
Comment 4 Rafael J. Wysocki 2008-09-01 12:43:20 UTC
On Monday, 1 of September 2008, Jaswinder Singh wrote:
> Hello all,
> 
> On Sat, Aug 30, 2008 at 3:50 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> >
> > The following bug entry is on the current list of known regressions
> > from 2.6.26.  Please verify if it still should be listed and let me know
> > (either way).
> >
> >
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=11271
> > Subject         : BUG: fealnx in 2.6.27-rc1
> > Submitter       : Jaswinder Singh <jaswinderlinux@gmail.com>
> > Date            : 2008-08-05 14:58 (26 days old)
> > References      : http://marc.info/?l=linux-netdev&m=121794762016830&w=4
> >                  http://lkml.org/lkml/2008/8/10/98
> > Handled-By      : Francois Romieu <romieu@fr.zoreil.com>
> >
> >
> >
> 
> Still exists in 2.6.27-rc5 :
> 
> NETDEV WATCHDOG: eth0 (fealnx): transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring f7b35000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring f7b36000:  80000000 80000000 80000000 80000000 0000 80000000
> ------------[ cut here ]------------
> WARNING: at net/sched/sch_generic.c:221 dev_watchdog+0x120/0x199()
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.27-rc5 #135
>  [<c011c977>] warn_on_slowpath+0x40/0x63
>  [<c0132dba>] tick_program_event+0x2b/0x4a
>  [<c012e194>] hrtimer_interrupt+0x136/0x15e
>  [<c010f69d>] smp_apic_timer_interrupt+0x6e/0x79
>  [<c01036c0>] apic_timer_interrupt+0x28/0x30
>  [<c038cfcc>] _spin_unlock_irqrestore+0x4/0x1a
>  [<c027b064>] tx_timeout+0x194/0x1d1
>  [<c0335085>] dev_watchdog+0x120/0x199
>  [<c012f96b>] getnstimeofday+0x32/0xb7
>  [<c0132060>] clockevents_program_event+0xca/0xd9
>  [<c0334f65>] dev_watchdog+0x0/0x199
>  [<c01234af>] run_timer_softirq+0xf5/0x14a
>  [<c01201ac>] __do_softirq+0x5d/0xc1
>  [<c0120242>] do_softirq+0x32/0x36
>  [<c0120378>] irq_exit+0x35/0x40
>  [<c010f69d>] smp_apic_timer_interrupt+0x6e/0x79
>  [<c01036c0>] apic_timer_interrupt+0x28/0x30
>  [<c010756c>] mwait_idle+0x32/0x3a
>  [<c0101924>] cpu_idle+0x5c/0x84
>  =======================
> ---[ end trace 65e715863a9afa94 ]---
> 

Comment 5 Rafael J. Wysocki 2008-09-01 12:43:56 UTC
On Monday, 1 of September 2008, Arjan van de Ven wrote:
> On Mon, 1 Sep 2008 13:02:29 -0400
> "Jaswinder Singh" <jaswinderlinux@gmail.com> wrote:
> 
> > 
> > Still exists in 2.6.27-rc5 :
> > 
> > NETDEV WATCHDOG: eth0 (fealnx): transmit timed out
> 
> 
> did you ever get transmit timeouts before 2.6.27 ?
> (I would suspect you did)

Comment 6 Rafael J. Wysocki 2008-09-01 12:44:47 UTC
On Monday, 1 of September 2008, Jaswinder Singh wrote:
>
> may be you are right, I have never noticed it earlier. But currently
> this is soo serious that it has totally screwed up my networking when
> I use fealnx based NICs.

Comment 7 Rafael J. Wysocki 2008-09-14 17:03:00 UTC
On Saturday, 13 of September 2008, Jaswinder Singh wrote:
> Hello all,
> 
> On Fri, Sep 12, 2008 at 3:06 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=11271
> > Subject         : BUG: fealnx in 2.6.27-rc1
> > Submitter       : Jaswinder Singh <jaswinderlinux@gmail.com>
> > Date            : 2008-08-05 14:58 (39 days old)
> > References      : http://marc.info/?l=linux-netdev&m=121794762016830&w=4
> >                  http://lkml.org/lkml/2008/8/10/98
> 
> I am sorry for delay.
> 
> Now I am testing for same problem with  2.6.27-rc6.:
> 1. On different MYSON Technology Inc SURECOM EP-320X-S 100/10M
> Ethernet PCI Adapters
> 2. On different Linux PCs
> 3. With different Ethernet switches which supports 100 Mb
> 4. With different CAT 5 ethernet cables which supports 100 Mb
> 5. Also checking old patches on fealnx as per Jeff.
> 
> And it seems, I am getting following error, with few ethernet switches
> and cables and when I switch ethernet cables  :
> "NETDEV WATCHDOG: eth0 (fealnx): transmit timed out
> eth0: Transmit timed out, status 00000000, resetting..."
> 
> Now I am trying to confirm that problem is coming from ethernet
> switches and cables.
> 
> I am also facing one more Issue :
> 
> With same 100 Mb ethernet switch and cable my another NIC run at 100
> Mb/s and full duplex but MYSON Technology Inc SURECOM EP-320X-S
> 100/10M runs on 10 Mb/s and half duplex.
> 
> I debug fealnx it says : PHYType 1 duplex_mode : 2 line_speed : 2
> crvalue : 0xe40e61 bcrvalue : 0x10 imrvalue : 0x46c flags : 0x1
> 
> So it is saying duplex_mode : 2 (full duplex) and line_speed = 2
> (100M) then why I am getting 10MB half duplex ?
> 
> #lspci -vv
> 02:02.0 Ethernet controller: MYSON Technology Inc SURECOM EP-320X-S
> 100/10M Ethernet PCI Adapter
>         Subsystem: MYSON Technology Inc SURECOM EP-320X-S 100/10M
> Ethernet PCI Adapter
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 64 bytes
>         Interrupt: pin A routed to IRQ 17
>         Region 0: I/O ports at b800 [size=256]
>         Region 1: Memory at ff9ffc00 (32-bit, non-prefetchable) [size=1K]
>         Expansion ROM at 50000000 [disabled] [size=64K]
>         Capabilities: [88] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA
> PME(D0-,D1+,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>         Kernel driver in use: fealnx
> 
> #/sbin/ethtool eth0
> Settings for eth0:
>         Supported ports: [ TP MII ]
>         Supported link modes:   10baseT/Half 10baseT/Full
>                                 100baseT/Half 100baseT/Full
>         Supports auto-negotiation: Yes
>         Advertised link modes:  Not reported
>         Advertised auto-negotiation: No
>         Speed: 10Mb/s
>         Duplex: Half
>         Port: MII
>         PHYAD: 32
>         Transceiver: internal
>         Auto-negotiation: off
>         Current message level: 0x00000000 (0)
>         Link detected: no

Comment 8 Jeff Garzik 2008-09-16 12:20:40 UTC
Created attachment 17812 [details]
Commit 28cd4289abc2c8db90344ee4ff064a9bdf086fdf

This is the only fealnx commit in recent memory.

Does reverting this patch help?

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