Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750773AbWJVSs7 (ORCPT ); Sun, 22 Oct 2006 14:48:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750819AbWJVSs7 (ORCPT ); Sun, 22 Oct 2006 14:48:59 -0400 Received: from smtp-out.google.com ([216.239.45.12]:55373 "EHLO smtp-out.google.com") by vger.kernel.org with ESMTP id S1750773AbWJVSs6 (ORCPT ); Sun, 22 Oct 2006 14:48:58 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:message-id:date:from:user-agent:mime-version:to: subject:content-type:content-transfer-encoding; b=WYTRLGZLYQ0nzfzNzP9ux20lAEFrhSXbzBV7j779mbNS61Pn6El3NkbzXqtKChEkm P/919QggAYaqJHubufoiw== Message-ID: <453BBC9E.4040300@google.com> Date: Sun, 22 Oct 2006 11:46:54 -0700 From: "Martin J. Bligh" User-Agent: Thunderbird 1.5.0.7 (X11/20060922) MIME-Version: 1.0 To: Linux Kernel Mailing List , netdev@vger.kernel.org Subject: Strange errors from e1000 driver (2.6.18) 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 Content-Length: 2764 Lines: 47 I'm getting a lot of these type of errors if I run 2.6.18. If I run the standard Ubuntu Dapper kernel, I don't get them. What do they indicate? Oct 21 18:48:28 localhost kernel: buffer_info[next_to_clean] Oct 21 18:48:28 localhost kernel: time_stamp <7b79d33> Oct 21 18:48:28 localhost kernel: next_to_watch <3d> Oct 21 18:48:28 localhost kernel: jiffies <7b7a0c1> Oct 21 18:48:28 localhost kernel: next_to_watch.status <0> Oct 21 18:48:30 localhost kernel: Tx Queue <0> Oct 21 18:48:30 localhost kernel: TDH <3d> Oct 21 18:48:30 localhost kernel: TDT <44> Oct 21 18:48:30 localhost kernel: next_to_use <44> Oct 21 18:48:30 localhost kernel: next_to_clean <39> Oct 21 18:48:30 localhost kernel: buffer_info[next_to_clean] Oct 21 18:48:30 localhost kernel: time_stamp <7b79d33> Oct 21 18:48:30 localhost kernel: next_to_watch <3d> Oct 21 18:48:30 localhost kernel: jiffies <7b7a2b5> Oct 21 18:48:30 localhost kernel: next_to_watch.status <0> Oct 21 18:48:32 localhost kernel: Tx Queue <0> Oct 21 18:48:32 localhost kernel: TDH <3d> Oct 21 18:48:32 localhost kernel: TDT <44> Oct 21 18:48:32 localhost kernel: next_to_use <44> Oct 21 18:48:32 localhost kernel: next_to_clean <39> Oct 21 18:48:32 localhost kernel: buffer_info[next_to_clean] Oct 21 18:48:32 localhost kernel: time_stamp <7b79d33> Oct 21 18:48:32 localhost kernel: next_to_watch <3d> Oct 21 18:48:32 localhost kernel: jiffies <7b7a4a9> Oct 21 18:48:32 localhost kernel: next_to_watch.status <0> Oct 21 18:48:34 localhost kernel: Tx Queue <0> Oct 21 18:48:34 localhost kernel: TDH <3d> Oct 21 18:48:34 localhost kernel: TDT <44> Oct 21 18:48:34 localhost kernel: next_to_use <44> Oct 21 18:48:34 localhost kernel: next_to_clean <39> Oct 21 18:48:34 localhost kernel: buffer_info[next_to_clean] Oct 21 18:48:34 localhost kernel: time_stamp <7b79d33> Oct 21 18:48:34 localhost kernel: next_to_watch <3d> Oct 21 18:48:34 localhost kernel: jiffies <7b7a69d> Oct 21 18:48:34 localhost kernel: next_to_watch.status <0> Oct 21 18:48:35 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out Oct 21 18:48:36 localhost kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/