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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3f9a31f40901020748m242c46djf153fbab90eeca60@mail.gmail.com>
Date:	Fri, 2 Jan 2009 21:18:35 +0530
From:	"Jaswinder Singh Rajput" <jaswinderlinux@...il.com>
To:	"Willy Tarreau" <w@....eu>
Cc:	wtarreau@...a.kernel.org, kernel-testers@...r.kernel.org,
	netdev@...r.kernel.org, jeff@...zik.org,
	linux-kernel@...r.kernel.org
Subject: Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out

Hello Willy,

On 1/2/09, Willy Tarreau <w@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/