All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Stuart <dstuart@rogers.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with disk + network on 2.6.25.11-60.fc8
Date: Mon, 04 Aug 2008 19:58:32 -0400	[thread overview]
Message-ID: <489797A8.408@rogers.com> (raw)
In-Reply-To: <20080805001330.6d43bcbb@lxorguk.ukuu.org.uk>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Alan Cox wrote:
> That would be great - if it makes no difference, yet high network traffic
> is the key factor then it mostly eliminates bugs in the network drivers
> from suspicion. At that point its time to dig deeper into the chip config.
>   

Hi Alan,

So I switched back to my old on-board network card (removing the prior 
card altogether from the case). I tried my test-case, which involves 
downloading some big files while simultaneously running a find command.

I *was* able to reproduce the issue fairly quickly.

The key difference is that this time I was using the skge kernel module 
for networking. So, I tend to agree that it is most likely not a network 
driver problem.

Please let me know if there is anything further I can do to assist in 
debugging.

Thanks,
David

-- 
The only way to keep your health is to eat what you don't want, drink
what you don't like, and do what you'd rather not.
                -- Mark Twain


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]

  reply	other threads:[~2008-08-04 23:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 17:39 Problems with disk + network on 2.6.25.11-60.fc8 David Stuart
2008-08-04 17:42 ` Alan Cox
2008-08-04 20:31   ` David Stuart
2008-08-04 20:44     ` Alan Cox
2008-08-04 23:27       ` David Stuart
2008-08-04 23:13         ` Alan Cox
2008-08-04 23:58           ` David Stuart [this message]
2008-08-07  1:43             ` David Stuart
2008-08-07 10:36               ` Alan Cox

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=489797A8.408@rogers.com \
    --to=dstuart@rogers.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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.