From: Dumitru Ciobarcianu <Dumitru.Ciobarcianu@iNES.RO>
To: "Martin J. Bligh" <mbligh@google.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: Strange errors from e1000 driver (2.6.18)
Date: Mon, 23 Oct 2006 02:02:43 +0300 [thread overview]
Message-ID: <1161558163.2720.4.camel@DustPuppy.LNX.RO> (raw)
In-Reply-To: <453BD41B.4010007@google.com>
On Sun, 2006-10-22 at 13:27 -0700, Martin J. Bligh wrote:
> Jesse Brandeburg wrote:
> > On 10/22/06, Martin J. Bligh <mbligh@mbligh.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,
>
> Sure.
>
> Handle 0x0001, DMI type 1, 25 bytes.
> System Information
> Manufacturer: VIA Technologies, Inc.
> Product Name: KT600-8237
> Version:
> Serial Number:
> UUID: Not Present
> Wake-up Type: Power Switch
If this matters: I've got the same errors with the fc5 kernel sometime
around january, also on an VIA-based motherboard. I only got around to
fix it by changing the motherboard... (worked fine with an intel-based
mb).
--
Cioby
prev parent reply other threads:[~2006-10-22 23:03 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
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 [this message]
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=1161558163.2720.4.camel@DustPuppy.LNX.RO \
--to=dumitru.ciobarcianu@ines.ro \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mbligh@mbligh.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox