BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out

All of lore.kernel.org
 help / color / mirror / Atom feed

* BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
@ 2009-01-02 14:40 ` Jaswinder Singh Rajput
  0 siblings, 0 replies; 9+ messages in thread
From: Jaswinder Singh Rajput @ 2009-01-02 14:40 UTC (permalink / raw)
  To: wtarreau-Dj75qbTlC0E76Z2rM5mHXA,
	kernel-testers-u79uwXL29TY76Z2rM5mHXA,
	netdev-u79uwXL29TY76Z2rM5mHXA, jeff-o2qLIJkoznsdnm+yROfE0A,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA

Hello all,

Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
"NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
can I fix this problem.

fealnx.c:v2.51 Nov-17-2001
eth0: 100/10M Ethernet PCI Adapter at 0x6200, 00:40:95:78:05:73, IRQ 11.

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
  Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring c11be000:  80000000 80000000 80000000 80000000 0000 80000000
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
  Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring c11be000:  80000000 0000 80000000 80000000 80000000 80000000
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
  Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring c11be000:  80000000 80000000 80000000 80000000 80000000 0000


00:0a.0 Ethernet controller: MYSON Technology Inc: Unknown device 0803
	Subsystem: MYSON Technology Inc: Unknown device 0803
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (8000ns min, 16000ns max), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 6200 [size=256]
	Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=1K]
	Expansion ROM at <unassigned> [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-

Thank you,
JSR

^ permalink raw reply	[flat|nested] 9+ messages in thread

* BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
@ 2009-01-02 14:40 ` Jaswinder Singh Rajput
  0 siblings, 0 replies; 9+ messages in thread
From: Jaswinder Singh Rajput @ 2009-01-02 14:40 UTC (permalink / raw)
  To: wtarreau, kernel-testers, netdev, jeff, linux-kernel

Hello all,

Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
"NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
can I fix this problem.

fealnx.c:v2.51 Nov-17-2001
eth0: 100/10M Ethernet PCI Adapter at 0x6200, 00:40:95:78:05:73, IRQ 11.

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
  Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring c11be000:  80000000 80000000 80000000 80000000 0000 80000000
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
  Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring c11be000:  80000000 0000 80000000 80000000 80000000 80000000
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 00000000, resetting...
  Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
80000000 80000000 80000000 80000000 80000000 80000000 80000000
  Tx ring c11be000:  80000000 80000000 80000000 80000000 80000000 0000


00:0a.0 Ethernet controller: MYSON Technology Inc: Unknown device 0803
	Subsystem: MYSON Technology Inc: Unknown device 0803
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (8000ns min, 16000ns max), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at 6200 [size=256]
	Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=1K]
	Expansion ROM at <unassigned> [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-

Thank you,
JSR

^ permalink raw reply	[flat|nested] 9+ messages in thread

[parent not found: <3f9a31f40901020640m4a9a63caq9c96ba84ccd64d88-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
  2009-01-02 14:40 ` Jaswinder Singh Rajput
@ 2009-01-02 14:48     ` Willy Tarreau
  -1 siblings, 0 replies; 9+ messages in thread
From: Willy Tarreau @ 2009-01-02 14:48 UTC (permalink / raw)
  To: Jaswinder Singh Rajput
  Cc: wtarreau-Dj75qbTlC0E76Z2rM5mHXA,
	kernel-testers-u79uwXL29TY76Z2rM5mHXA,
	netdev-u79uwXL29TY76Z2rM5mHXA, jeff-o2qLIJkoznsdnm+yROfE0A,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA

Hello,

On Fri, Jan 02, 2009 at 08:10:50PM +0530, Jaswinder Singh Rajput wrote:
> Hello all,
> 
> Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
> "NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
> can I fix this problem.

Well, I don't have such an adapter, but most of the times I encountered
a similar message with older 10/100 adapters, it was caused by a link
status issue or duplex mismatch.

Could you check with ethtool or mii-diag that the link status is correct
and 100 Mbps/Full duplex (assuming you're connected to a switch) ?

> fealnx.c:v2.51 Nov-17-2001
> eth0: 100/10M Ethernet PCI Adapter at 0x6200, 00:40:95:78:05:73, IRQ 11.
> 
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring c11be000:  80000000 80000000 80000000 80000000 0000 80000000
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring c11be000:  80000000 0000 80000000 80000000 80000000 80000000
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring c11be000:  80000000 80000000 80000000 80000000 80000000 0000
> 
> 
> 00:0a.0 Ethernet controller: MYSON Technology Inc: Unknown device 0803
> 	Subsystem: MYSON Technology Inc: Unknown device 0803
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> 	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> 	Latency: 32 (8000ns min, 16000ns max), cache line size 08
> 	Interrupt: pin A routed to IRQ 11
> 	Region 0: I/O ports at 6200 [size=256]
> 	Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=1K]
> 	Expansion ROM at <unassigned> [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-
> 
> Thank you,
> JSR

Regards,
Willy

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
@ 2009-01-02 14:48     ` Willy Tarreau
  0 siblings, 0 replies; 9+ messages in thread
From: Willy Tarreau @ 2009-01-02 14:48 UTC (permalink / raw)
  To: Jaswinder Singh Rajput
  Cc: wtarreau, kernel-testers, netdev, jeff, linux-kernel

Hello,

On Fri, Jan 02, 2009 at 08:10:50PM +0530, Jaswinder Singh Rajput wrote:
> Hello all,
> 
> Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
> "NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
> can I fix this problem.

Well, I don't have such an adapter, but most of the times I encountered
a similar message with older 10/100 adapters, it was caused by a link
status issue or duplex mismatch.

Could you check with ethtool or mii-diag that the link status is correct
and 100 Mbps/Full duplex (assuming you're connected to a switch) ?

> fealnx.c:v2.51 Nov-17-2001
> eth0: 100/10M Ethernet PCI Adapter at 0x6200, 00:40:95:78:05:73, IRQ 11.
> 
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring c11be000:  80000000 80000000 80000000 80000000 0000 80000000
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring c11be000:  80000000 0000 80000000 80000000 80000000 80000000
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 00000000, resetting...
>   Rx ring c11bf000:  80000000 80000000 80000000 80000000 80000000
> 80000000 80000000 80000000 80000000 80000000 80000000 80000000
>   Tx ring c11be000:  80000000 80000000 80000000 80000000 80000000 0000
> 
> 
> 00:0a.0 Ethernet controller: MYSON Technology Inc: Unknown device 0803
> 	Subsystem: MYSON Technology Inc: Unknown device 0803
> 	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> 	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> 	Latency: 32 (8000ns min, 16000ns max), cache line size 08
> 	Interrupt: pin A routed to IRQ 11
> 	Region 0: I/O ports at 6200 [size=256]
> 	Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=1K]
> 	Expansion ROM at <unassigned> [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-
> 
> Thank you,
> JSR

Regards,
Willy


^ permalink raw reply	[flat|nested] 9+ messages in thread

[parent not found: <20090102144813.GA13757-K+wRfnb2/UA@public.gmane.org>]

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
  2009-01-02 14:48     ` Willy Tarreau
@ 2009-01-02 15:48         ` Jaswinder Singh Rajput
  -1 siblings, 0 replies; 9+ messages in thread
From: Jaswinder Singh Rajput @ 2009-01-02 15:48 UTC (permalink / raw)
  To: Willy Tarreau
  Cc: wtarreau-Dj75qbTlC0E76Z2rM5mHXA,
	kernel-testers-u79uwXL29TY76Z2rM5mHXA,
	netdev-u79uwXL29TY76Z2rM5mHXA, jeff-o2qLIJkoznsdnm+yROfE0A,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA

Hello Willy,

On 1/2/09, Willy Tarreau <w@1wt.eu> wrote:
> On Fri, Jan 02, 2009 at 08:10:50PM +0530, Jaswinder Singh Rajput wrote:
>> Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
>> "NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
>> can I fix this problem.
>
> Well, I don't have such an adapter, but most of the times I encountered
> a similar message with older 10/100 adapters, it was caused by a link
> status issue or duplex mismatch.
>
I think I am also getting same problem, what is the solution.

> Could you check with ethtool or mii-diag that the link status is correct
> and 100 Mbps/Full duplex (assuming you're connected to a switch) ?
>

Output of mii-diag -v :
eth0: 10 Mbit, half duplex, no link
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:

This is the output from very old machine Pentium MMX with Redhat 7.1

I also tested different RTL8139 adapters on different machines with
different kernels and different kind of switches and Hubs but I get
same error on all the machines. But my other Network devices are
working perfectly.

Thank you,
JSR

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
@ 2009-01-02 15:48         ` Jaswinder Singh Rajput
  0 siblings, 0 replies; 9+ messages in thread
From: Jaswinder Singh Rajput @ 2009-01-02 15:48 UTC (permalink / raw)
  To: Willy Tarreau; +Cc: wtarreau, kernel-testers, netdev, jeff, linux-kernel

Hello Willy,

On 1/2/09, Willy Tarreau <w@1wt.eu> wrote:
> On Fri, Jan 02, 2009 at 08:10:50PM +0530, Jaswinder Singh Rajput wrote:
>> Now I tested fealnx driver from 2.4.37 (2.4 git). I am still getting
>> "NETDEV WATCHDOG: eth0: transmit timed out". Please let me know how
>> can I fix this problem.
>
> Well, I don't have such an adapter, but most of the times I encountered
> a similar message with older 10/100 adapters, it was caused by a link
> status issue or duplex mismatch.
>
I think I am also getting same problem, what is the solution.

> Could you check with ethtool or mii-diag that the link status is correct
> and 100 Mbps/Full duplex (assuming you're connected to a switch) ?
>

Output of mii-diag -v :
eth0: 10 Mbit, half duplex, no link
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:

This is the output from very old machine Pentium MMX with Redhat 7.1

I also tested different RTL8139 adapters on different machines with
different kernels and different kind of switches and Hubs but I get
same error on all the machines. But my other Network devices are
working perfectly.

Thank you,
JSR

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
  2009-01-02 15:48         ` Jaswinder Singh Rajput
  (?)
@ 2009-01-02 18:57         ` Francois Romieu
       [not found]           ` <20090102185718.GB20741-lmTtMILVy1jWQcoT9B9Ug5SCg42XY1Uw0E9HWUfgJXw@public.gmane.org>
  -1 siblings, 1 reply; 9+ messages in thread
From: Francois Romieu @ 2009-01-02 18:57 UTC (permalink / raw)
  To: Jaswinder Singh Rajput
  Cc: Willy Tarreau, wtarreau, kernel-testers, netdev, jeff,
	linux-kernel

Jaswinder Singh Rajput <jaswinderlinux@gmail.com> :
[..]
> Output of mii-diag -v :
> eth0: 10 Mbit, half duplex, no link
>   product info: vendor 00:00:00, model 0 rev 0
>   basic mode:   10 Mbit, half duplex
>   basic status: no link
>   capabilities:
>   advertising:
> 
> This is the output from very old machine Pentium MMX with Redhat 7.1

Can you check with 'mii-tool -vv eth0' that the mii registers are not
all zeroes ?

-- 
Ueimor

^ permalink raw reply	[flat|nested] 9+ messages in thread

[parent not found: <20090102185718.GB20741-lmTtMILVy1jWQcoT9B9Ug5SCg42XY1Uw0E9HWUfgJXw@public.gmane.org>]

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
  2009-01-02 18:57         ` Francois Romieu
@ 2009-01-03 11:10               ` Jaswinder Singh Rajput
  0 siblings, 0 replies; 9+ messages in thread
From: Jaswinder Singh Rajput @ 2009-01-03 11:10 UTC (permalink / raw)
  To: Francois Romieu
  Cc: Willy Tarreau, wtarreau-Dj75qbTlC0E76Z2rM5mHXA,
	kernel-testers-u79uwXL29TY76Z2rM5mHXA,
	netdev-u79uwXL29TY76Z2rM5mHXA, jeff-o2qLIJkoznsdnm+yROfE0A,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA

On Sat, Jan 3, 2009 at 12:27 AM, Francois Romieu <romieu-W8zweXLXuWQS+FvcfC7Uqw@public.gmane.org> wrote:
> Jaswinder Singh Rajput <jaswinderlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> :
> [..]
>> Output of mii-diag -v :
>> eth0: 10 Mbit, half duplex, no link
>>   product info: vendor 00:00:00, model 0 rev 0
>>   basic mode:   10 Mbit, half duplex
>>   basic status: no link
>>   capabilities:
>>   advertising:
>>
>> This is the output from very old machine Pentium MMX with Redhat 7.1
>
> Can you check with 'mii-tool -vv eth0' that the mii registers are not
> all zeroes ?
>

Yes all are zeros :-)

eth0: 10 Mbit, half duplex, no link
  registers for MII PHY 32:
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:

Now what is next step.

Thank you,
JSR

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
@ 2009-01-03 11:10               ` Jaswinder Singh Rajput
  0 siblings, 0 replies; 9+ messages in thread
From: Jaswinder Singh Rajput @ 2009-01-03 11:10 UTC (permalink / raw)
  To: Francois Romieu
  Cc: Willy Tarreau, wtarreau, kernel-testers, netdev, jeff,
	linux-kernel

On Sat, Jan 3, 2009 at 12:27 AM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Jaswinder Singh Rajput <jaswinderlinux@gmail.com> :
> [..]
>> Output of mii-diag -v :
>> eth0: 10 Mbit, half duplex, no link
>>   product info: vendor 00:00:00, model 0 rev 0
>>   basic mode:   10 Mbit, half duplex
>>   basic status: no link
>>   capabilities:
>>   advertising:
>>
>> This is the output from very old machine Pentium MMX with Redhat 7.1
>
> Can you check with 'mii-tool -vv eth0' that the mii registers are not
> all zeroes ?
>

Yes all are zeros :-)

eth0: 10 Mbit, half duplex, no link
  registers for MII PHY 32:
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
    0000 0000 0000 0000 0000 0000 0000 0000
  product info: vendor 00:00:00, model 0 rev 0
  basic mode:   10 Mbit, half duplex
  basic status: no link
  capabilities:
  advertising:

Now what is next step.

Thank you,
JSR

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2009-01-03 11:10 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-02 14:40 BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out Jaswinder Singh Rajput
2009-01-02 14:40 ` Jaswinder Singh Rajput
     [not found] ` <3f9a31f40901020640m4a9a63caq9c96ba84ccd64d88-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-02 14:48   ` Willy Tarreau
2009-01-02 14:48     ` Willy Tarreau
     [not found]     ` <20090102144813.GA13757-K+wRfnb2/UA@public.gmane.org>
2009-01-02 15:48       ` Jaswinder Singh Rajput
2009-01-02 15:48         ` Jaswinder Singh Rajput
2009-01-02 18:57         ` Francois Romieu
     [not found]           ` <20090102185718.GB20741-lmTtMILVy1jWQcoT9B9Ug5SCg42XY1Uw0E9HWUfgJXw@public.gmane.org>
2009-01-03 11:10             ` Jaswinder Singh Rajput
2009-01-03 11:10               ` Jaswinder Singh Rajput

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.