From: Carsten Otto <c-otto@gmx.de>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: linux-kernel@vger.kernel.org, NetDEV list <netdev@vger.kernel.org>
Subject: Re: Intel e1000 fails after RAM upgrade
Date: Tue, 20 Dec 2005 01:47:52 +0100 [thread overview]
Message-ID: <20051220004752.GA19114@carsten-otto.halifax.rwth-aachen.de> (raw)
In-Reply-To: <4807377b0512191535i13d00b8chd97872b3e540e2b5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Mon, Dec 19, 2005 at 03:35:57PM -0800, Jesse Brandeburg wrote:
> > TDH <2000>
> > TDT <2000>
> > next_to_use <6>
> > next_to_clean <0>
> > buffer_info[next_to_clean]
> > dma <13024c002>
> > time_stamp <ffffd8c7>
> > next_to_watch <0>
> > jiffies <ffffe096>
> > next_to_watch.status <0>
>
> are you using 4096 tx descriptors? what is your MTU configured to?
> I'm confused because it appears you have 8192 (0x2000) descriptors but
> the driver only allows 4096
I am not. My MTU is 1500. At the moment the error message is:
TDH <0>
TDT <3>
next_to_use <3>
next_to_clean <0>
buffer_info[next_to_clean]
dma <128d61202>
time_stamp <100026052>
next_to_watch <0>
jiffies <10002667c>
next_to_watch.status <0>
I can't reproduce the 2000 value.
PS: The problem does not occur with Knoppix 3.9.
Thanks for the help,
--
Carsten Otto
c-otto@gmx.de
www.c-otto.de
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-12-20 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051219195458.GA23650@carsten-otto.halifax.rwth-aachen.de>
2005-12-19 23:35 ` Intel e1000 fails after RAM upgrade Jesse Brandeburg
2005-12-20 0:47 ` Carsten Otto [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=20051220004752.GA19114@carsten-otto.halifax.rwth-aachen.de \
--to=c-otto@gmx.de \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.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