From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753437AbYFTJiM (ORCPT ); Fri, 20 Jun 2008 05:38:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751464AbYFTJh6 (ORCPT ); Fri, 20 Jun 2008 05:37:58 -0400 Received: from lana.hrz.tu-chemnitz.de ([134.109.132.3]:50621 "EHLO lana.hrz.tu-chemnitz.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751346AbYFTJh5 (ORCPT ); Fri, 20 Jun 2008 05:37:57 -0400 X-Greylist: delayed 2718 seconds by postgrey-1.27 at vger.kernel.org; Fri, 20 Jun 2008 05:37:56 EDT Date: Fri, 20 Jun 2008 10:52:36 +0200 From: Steffen Klassert To: mt@systella.fr, linux-kernel@vger.kernel.org Subject: Re: NETDEV WATCHDOG on U60/SMP Message-ID: <20080620085236.GA2376@bayes.mathematik.tu-chemnitz.de> References: <485B6218.4090705@systella.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <485B6218.4090705@systella.fr> User-Agent: Mutt/1.4.2.1i X-Spam-Score: -1.4 (-) X-Spam-Report: --- Start der SpamAssassin 3.2.5 Textanalyse (-1.4 Punkte) Fragen an/questions to: Postmaster TU Chemnitz -1.4 ALL_TRUSTED Nachricht wurde nur ueber vertrauenswuerdige Rechner weitergeleitet --- Ende der SpamAssassin Textanalyse X-Scan-Signature: 439a779e86734b9f9e658ea38d6cb1c3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 20, 2008 at 09:54:00AM +0200, BERTRAND Jo?l wrote: > Hello, > > This mail comes from sparclinux mailing list. I repost it on general > linux kernel mailing list because I'm not sure that this bug is sparc > specific. Nevertheless, I can only reproduce it on sparc64/SMP. > > My U60 runs linux debian with official 2.6.25 linux kernel (I'm > currently trying 2.6.25.7) and sometimes, when eth2 is stressed, eth2 > hangs with NETDEV WATCHDOG : > > NETDEV WATCHDOG: eth2: transmit timed out > eth2: transmit timed out, tx_status 00 status 8601. > diagnostics: net 0ccc media 8880 dma 0000003a fifo 0000 > eth2: Interrupt posted but not delivered -- IRQ blocked by another device? > Flags; bus-master 1, dirty 2283344(0) current 2283344(0) > Transmit list 00000000 vs. fffff800af098200. > 0: @fffff800af098200 length 00000042 status 0c01059a > 1: @fffff800af098260 length 00000042 status 0c01059a > 2: @fffff800af0982c0 length 00000042 status 0c01059a > 3: @fffff800af098320 length 00000042 status 0c01059a > 4: @fffff800af098380 length 00000042 status 0c01059a > 5: @fffff800af0983e0 length 00000042 status 0c01059a > 6: @fffff800af098440 length 00000042 status 0c01059a > 7: @fffff800af0984a0 length 00000042 status 0c01059a > 8: @fffff800af098500 length 8000002a status 0001002a > 9: @fffff800af098560 length 8000002a status 0001002a > 10: @fffff800af0985c0 length 8000002a status 0001002a > 11: @fffff800af098620 length 8000002a status 0001002a > 12: @fffff800af098680 length 8000002a status 0001002a > 13: @fffff800af0986e0 length 8000002a status 0001002a > 14: @fffff800af098740 length 8000002a status 8001002a > 15: @fffff800af0987a0 length 8000002a status 8001002a > eth2: Resetting the Tx ring pointer. > eth2: setting full-duplex. Some people with similar problems reported, that they can workarround their problems by increasing the rx/tx ring sizes of the 3c59x driver. See http://bugzilla.kernel.org/show_bug.cgi?id=6444 for details. Would be good to know whether this helps for your problem too. Steffen