From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934722AbZAOU7w (ORCPT ); Thu, 15 Jan 2009 15:59:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933030AbZAOUUm (ORCPT ); Thu, 15 Jan 2009 15:20:42 -0500 Received: from electric-eye.fr.zoreil.com ([213.41.134.224]:46498 "EHLO electric-eye.fr.zoreil.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932945AbZAOUUk (ORCPT ); Thu, 15 Jan 2009 15:20:40 -0500 Date: Thu, 15 Jan 2009 21:21:04 +0100 From: Francois Romieu To: Justin Piszcz Cc: Andrew Morton , linux-kernel@vger.kernel.org, Alan Piszcz , netdev@vger.kernel.org Subject: Re: 2.6.28: r8169: NETDEV WATCHDOG: eth0 (r8169): transmit timed out Message-ID: <20090115202104.GA32495@electric-eye.fr.zoreil.com> References: <20090114213618.a610d647.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Organisation: Land of Sunshine Inc. User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Justin Piszcz : [...] > It is the first time I have ever seen it on this system, while running > 2.6.28. I have never seen the error in the past (at least not that I can > remember/no log entries) for 2.6.27 or below. Does it translate into a temporary network hiccup, say a few seconds, or does it mean a final loss of networking ? Given the timestamp, the driver seemed to worked for some amount of time before breaking, did it not ? It would thus be different from the usual "no link at startup" problem. Can you send a complete dmesg, including the r8169 XID line ? -- Ueimor