public inbox for linux-kernel@vger.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:27:53 -0400	[thread overview]
Message-ID: <48979079.9030409@rogers.com> (raw)
In-Reply-To: <20080804214441.0811138e@lxorguk.ukuu.org.uk>

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

Alan Cox wrote:
> Ok so the pdc202xx_old hardware flakes out when you have very high
> network load (I'd guess in fact very high bus traffic).
>
> The actual log is the disk I/O timing out, then the drive being busy
> (probably due to the timeout and a DMA transfer getting stuck). We reset
> it and carry on.
>
> Libata happens to log this a lot more visibly than old kernels which is
> useful but does mean people sometimes don't notice.
>
> The rest then fits - the freeze I'd expect as we block I/O while trying
> to get the drive back.
>
> Doubt the Nvidia module is involved as I'd then expect problems under
> high graphical load but you can certainly test that. I don't suppose
> you've got a spare PCI network card you could try instead to see if it is
> the network card bits ?
>
> Alan
>   

Hi Alan,

Actually I do not really have another PCI network card, but I could 
switch the computer back to the other interface which is on the 
motherboard (does that one function as a PCI device?). As I mentioned in 
my first post, the current card I am using is an attempt to try to work 
around the problem (originally I thought it was the on-board 
controller), so I have my doubts as to whether switching back would help.

Nonetheless, I will give it a try again and let you know the result.

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:28 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 [this message]
2008-08-04 23:13         ` Alan Cox
2008-08-04 23:58           ` David Stuart
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=48979079.9030409@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox