From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751055AbWGGPYz (ORCPT ); Fri, 7 Jul 2006 11:24:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751082AbWGGPYz (ORCPT ); Fri, 7 Jul 2006 11:24:55 -0400 Received: from tornado.reub.net ([202.89.145.182]:3307 "EHLO tornado.reub.net") by vger.kernel.org with ESMTP id S1751049AbWGGPYy (ORCPT ); Fri, 7 Jul 2006 11:24:54 -0400 Message-ID: <44AE7CC6.6090202@reub.net> Date: Sat, 08 Jul 2006 03:24:54 +1200 From: Reuben Farrelly User-Agent: Thunderbird 3.0a1 (Windows/20060707) MIME-Version: 1.0 To: Andrew Morton CC: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: 2.6.17-mm6 References: <20060703030355.420c7155.akpm@osdl.org> In-Reply-To: <20060703030355.420c7155.akpm@osdl.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 3/07/2006 10:03 p.m., Andrew Morton wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm6/ > > > - A major update to the e1000 driver. > > - 1394 updates Some minor breakage in the e1000... Fedora Core release 5.90 (Test) Kernel 2.6.17-mm6 on an x86_64 tornado.reub.net login: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH TDT <1c> next_to_use <1c> next_to_clean <8> buffer_info[next_to_clean] time_stamp <100027f1a> next_to_watch jiffies <1000281d4> next_to_watch.status <0> e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH TDT <1c> next_to_use <1c> next_to_clean <8> buffer_info[next_to_clean] time_stamp <100027f1a> next_to_watch jiffies <1000283c8> next_to_watch.status <0> e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH TDT <1c> next_to_use <1c> next_to_clean <8> buffer_info[next_to_clean] time_stamp <100027f1a> next_to_watch jiffies <1000285bc> next_to_watch.status <0> e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH TDT <1c> next_to_use <1c> next_to_clean <8> buffer_info[next_to_clean] time_stamp <100027f1a> next_to_watch jiffies <1000287b0> next_to_watch.status <0> e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Tx Queue <0> TDH TDT <1c> next_to_use <1c> next_to_clean <8> buffer_info[next_to_clean] time_stamp <100027f1a> next_to_watch jiffies <1000289a4> next_to_watch.status <0> A look through my switch logs and kernel logs over the last few days shows these messages and layer 2/link down disconnections every few hours or so, but of very short duration (I hadn't noticed until now). This output above was under virtually no load. Both the e1000 and switch port on the other end are doing RX and TX flow control. The controller is a built in chip on an Intel D945GNT board. 01:00.0 Ethernet controller: Intel Corporation 82573V Gigabit Ethernet Controller (Copper) (rev 03) Subsystem: Intel Corporation Unknown device 3094 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-