mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
To: "Willy Tarreau" <w@1wt.eu>
Cc: wtarreau@hera.kernel.org, kernel-testers@vger.kernel.org,
	netdev@vger.kernel.org, jeff@garzik.org,
	linux-kernel@vger.kernel.org
Subject: Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out
Date: Fri, 2 Jan 2009 21:18:35 +0530	[thread overview]
Message-ID: <3f9a31f40901020748m242c46djf153fbab90eeca60@mail.gmail.com> (raw)
In-Reply-To: <20090102144813.GA13757@1wt.eu>

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

  reply	other threads:[~2009-01-02 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 14:40 Jaswinder Singh Rajput
2009-01-02 14:48 ` Willy Tarreau
2009-01-02 15:48   ` Jaswinder Singh Rajput [this message]
2009-01-02 18:57     ` Francois Romieu
2009-01-03 11:10       ` Jaswinder Singh Rajput

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3f9a31f40901020748m242c46djf153fbab90eeca60@mail.gmail.com \
    --to=jaswinderlinux@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=w@1wt.eu \
    --cc=wtarreau@hera.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®