All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Nathan Grennan <alistair@cygnusx-1.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-net@vger.kernel.org
Subject: Re: r8169 and out of space
Date: Thu, 10 Jan 2008 19:20:46 +0000	[thread overview]
Message-ID: <200801101920.47041.alistair@devzero.co.uk> (raw)
In-Reply-To: <478655B6.6010406@cygnusx-1.org>

Bugzilla for this report: http://bugzilla.kernel.org/show_bug.cgi?id=9468

On Thursday 10 January 2008 17:28:22 you wrote:
>   I saw your thread on LKML about the problem with r8169. Did you ever
> find a patch or solution?

No, we have not diagnosed the cause of the problem, beyond the swiotlb usage. 
I'm adding the r8169 maintainer, linux-net and linux-kernel to CC, to pass on 
your information, I hope you don't mind.

>   I have a Abit AB9 Pro motherboard with Intel P965 chipset, 4gb of
> memory, and two onboard r8169. The kernel is
> kernel-2.6.23.9-85.fc8.x86_64. I am using jumbo frames, the MTU set at
> 5924. The error is mentions 5946 bytes. 5946 - 5924 is 22. The same as
> your 7200 MTU subtracted from your bytes, 7222.
>
>   I can set my MTU to 7200, and I can ping with 60000 byte packets just
> fine, but tcp connections hang unless I set the MTU to 5924 or lower.
> The other side is a Nvidia based board with a forcedeth driver that has
> in the past taken 9000 just fine.

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.

       reply	other threads:[~2008-01-10 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <478655B6.6010406@cygnusx-1.org>
2008-01-10 19:20 ` Alistair John Strachan [this message]
2008-01-10 20:57   ` r8169 and out of space Francois Romieu
2008-01-10 21:39     ` Nathan Grennan
2008-01-11  4:54     ` Nathan Grennan

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=200801101920.47041.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=alistair@cygnusx-1.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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.