From: "Martin J. Bligh" <mbligh@mbligh.org>
To: "Martin J. Bligh" <mbligh@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Strange errors from e1000 driver (2.6.18)
Date: Sun, 22 Oct 2006 12:05:11 -0700 [thread overview]
Message-ID: <453BC0E7.1060308@mbligh.org> (raw)
In-Reply-To: <453BBC9E.4040300@google.com>
Martin J. Bligh wrote:
> 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
Actually, maybe this set is more helpful:
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <6>
TDT <1f>
next_to_use <1f>
next_to_clean <2>
buffer_info[next_to_clean]
time_stamp <2de8b54>
next_to_watch <6>
jiffies <2de8db7>
next_to_watch.status <0>
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <6>
TDT <1f>
next_to_use <1f>
next_to_clean <2>
buffer_info[next_to_clean]
time_stamp <2de8b54>
next_to_watch <6>
jiffies <2de8fab>
next_to_watch.status <0>
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH <6>
TDT <1f>
next_to_use <1f>
next_to_clean <2>
buffer_info[next_to_clean]
time_stamp <2de8b54>
next_to_watch <6>
jiffies <2de919f>
next_to_watch.status <0>
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
next prev parent reply other threads:[~2006-10-22 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 18:46 Strange errors from e1000 driver (2.6.18) Martin J. Bligh
2006-10-22 19:05 ` Martin J. Bligh [this message]
2006-10-22 20:21 ` Jesse Brandeburg
2006-10-22 20:27 ` Martin J. Bligh
2006-10-22 22:15 ` Jesse Brandeburg
2006-10-22 22:32 ` Martin J. Bligh
2006-10-22 23:29 ` Jesse Brandeburg
2006-10-22 23:02 ` Dumitru Ciobarcianu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453BC0E7.1060308@mbligh.org \
--to=mbligh@mbligh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.