linux-kernel - Re: Strange errors from e1000 driver (2.6.18)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4807377b0610221321i62455faende025f88142dd087@mail.gmail.com>
Date:	Sun, 22 Oct 2006 13:21:40 -0700
From:	"Jesse Brandeburg" <jesse.brandeburg@...il.com>
To:	"Martin J. Bligh" <mbligh@...igh.org>
Cc:	"Martin J. Bligh" <mbligh@...gle.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org
Subject: Re: Strange errors from e1000 driver (2.6.18)

On 10/22/06, Martin J. Bligh <mbligh@...igh.org> wrote:
> 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?

Hi Martin, they indicate that you're getting transmit hangs.  Means
your hardware is having issues with some of the buffers it is being
handed.  Because the TDH and TDT noted below are not equal, it means
the hardware is hung processing buffers that the driver gave to it.

We need the standard bug report particulars, lspci -vv, cat
/proc/interrupts, dmesg, ethtool -e eth0, and maybe output of
dmidecode, etc.  I'm pretty sure you know the drill.

> > 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>
<snip>

> 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>
<snip>
> NETDEV WATCHDOG: eth0: transmit timed out
> e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex

only a little.  There are so many different pieces of e1000 hardware
and so few specifics in this report that I'll be able to tell you lots
more when you get us the info requested.

Jesse
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/