public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Van Maren, Kevin" <kevin.vanmaren@unisys.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Basic Advice Needed
Date: Tue, 02 Apr 2002 15:14:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905362@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905348@msgid-missing>

> As someone pointed out, the network and SCSI adapters may be causing
> problems. It has an Adaptec Ultra160 dual channel SCSI card for
> example, which definitely seems nonstandard.

Yes, that card works well -- if you have the right driver.

Use the latest Adaptec driver from Justin Gibbs.  There was a bug in the
early 39-bit DMA support that caused the kernel to crash periodically
[if the address just happened to overlab the swiotlb in the low 32 bits].

He incorporated my fix in Change 420:
http://people.freebsd.org/~gibbs/linux/

If you want to see if that affects you, look at the call to
pci_unmap_single();
if the second parameter is:
   ahc_le32toh(scb->sg_list[0].addr),
you have the broken version.  Note that the 2.4.9 kernel has the broken
version,
and IA64 kernels before that didn't support 39-bit DMA (which leads to
problems
under load, unless you greatly increase swiotlb size).  Not sure what
version
is in the newer IA64 kernels.

Kevin


  parent reply	other threads:[~2002-04-02 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-01  3:20 [Linux-ia64] Basic Advice Needed Jeremy Fox
2002-04-01  3:30 ` Randolph Chung
2002-04-01  7:24 ` Jeremy Fox
2002-04-01 14:42 ` Van Maren, Kevin
2002-04-01 15:25 ` n0ano
2002-04-01 16:17 ` Andreas Schwab
2002-04-01 23:18 ` Jeremy Fox
2002-04-02  7:52 ` Andreas Schwab
2002-04-02  8:29 ` Gwenole Beauchesne
2002-04-02 15:14 ` Van Maren, Kevin [this message]
2002-04-03  0:17 ` Jeremy Fox

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=marc-linux-ia64-105590701905362@msgid-missing \
    --to=kevin.vanmaren@unisys.com \
    --cc=linux-ia64@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