From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758186AbZABPs4 (ORCPT ); Fri, 2 Jan 2009 10:48:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757862AbZABPsj (ORCPT ); Fri, 2 Jan 2009 10:48:39 -0500 Received: from wa-out-1112.google.com ([209.85.146.180]:35301 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757873AbZABPsh (ORCPT ); Fri, 2 Jan 2009 10:48:37 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ZMn6sORR819ZWKZfXhxYZr9R1G3GQad+KYWq2fPDr3snh1XEgsIMqdTjrqxu7D9+Sf o70wMqeaNW1bNXywmcO/K8mugQ5U1nRDAdjyAUx0wGKQYcAFuKLuf5dPgWjq5nGvLUtX /38HrkwFU7tzaGe8rtdOVq6AlqZNnKyqpoArk= Message-ID: <3f9a31f40901020748m242c46djf153fbab90eeca60@mail.gmail.com> Date: Fri, 2 Jan 2009 21:18:35 +0530 From: "Jaswinder Singh Rajput" To: "Willy Tarreau" Subject: Re: BUG - 2.4.37 fealnx.c NETDEV WATCHDOG: eth0: transmit timed out Cc: wtarreau@hera.kernel.org, kernel-testers@vger.kernel.org, netdev@vger.kernel.org, jeff@garzik.org, linux-kernel@vger.kernel.org In-Reply-To: <20090102144813.GA13757@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3f9a31f40901020640m4a9a63caq9c96ba84ccd64d88@mail.gmail.com> <20090102144813.GA13757@1wt.eu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Willy, On 1/2/09, Willy Tarreau 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