mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <joerg.beyer@email.de>
To: joerg.beyer@email.de, "ZwaneMwaikambo" <zwane@linuxpower.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: Re: <no subject>
Date: Mon, 26 Aug 2002 12:54:41 +0200	[thread overview]
Message-ID: <200208261054.g7QAsfX06008@mailgate5.cinetic.de> (raw)

Zwane Mwaikambo <zwane@linuxpower.ca> schrieb am 25.08.02 14:10:12:
> On Sun, 25 Aug 2002 joerg.beyer@email.de wrote:
> 
> > you are right, I had no dma enabled. Now I recomiled the kernel with this
> > dma-related options:
> > 
> > CONFIG_BLK_DEV_IDEDMA_PCI=y
> > # CONFIG_BLK_DEV_IDEDMA_FORCED is not set
> > CONFIG_IDEDMA_PCI_AUTO=y
> > # CONFIG_IDEDMA_ONLYDISK is not set
> > CONFIG_BLK_DEV_IDEDMA=y
> > # CONFIG_IDEDMA_PCI_WIP is not set
> > # CONFIG_BLK_DEV_IDEDMA_TIMEOUT is not set
> > # CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
> > CONFIG_BLK_DEV_ADMA=y
> > # CONFIG_HPT34X_AUTODMA is not set
> > CONFIG_IDEDMA_AUTO=y
> > # CONFIG_IDEDMA_IVB is not set
> > # CONFIG_DMA_NONPCI is not set
> > 
> > 
> > and I still get many many errors on the nic. Do I need something more in .config?
> 
> That should fix your slowdown during untarring/disk access, as for your 
> NIC problem looks like you might be having a receive FIFO overflow, so 
> perhaps the card stops processing incoming packets? I have no clue, 
> Jeff?

is it possible, that I made a simmilar mistake at the NIC module configuration
and that I dont use dma at the NIC?

Put it the ohter way round: how could I see if the 8139too NIC module
uses DMA?

It is supposed to use DMA, right?

   Joerg


             reply	other threads:[~2002-08-26 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 10:54 joerg.beyer [this message]
2002-08-26 12:20 ` Zwane Mwaikambo
2002-08-26 13:16 joerg.beyer
2002-08-26 18:55 joerg.beyer

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=200208261054.g7QAsfX06008@mailgate5.cinetic.de \
    --to=joerg.beyer@email.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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

all inboxes | Powered by JetHome®