mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Celistica with AMD chip-set
Date: Mon, 30 Aug 2004 10:02:32 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0408300955470.21607@chaos> (raw)


Hello all,

The Celistica server with the AMD chip-set has very poor
PCI performance with Linux (and probably W$ too).

The problem was traced to incorrect bridge configuration
in the HyperTransport(tm) chips that connect up pairs
of slots.

I don't know how to make a generic chip-set bug-fix, and
probably a new BIOS will come out with the correct values
in the registers. But right now, the following initialization
code will fix the box.



//-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
//
//  Some kind of problem, here. If the HyperTransport(tm) bridge
//  is found, one of the register values needs to be changed to
//  fix the bus performance. Need to turn back on prefetch.
//

    while((pdev = pci_find_device(0x1022, 0x7450, pdev)) != NULL)
        pci_write_config_dword(pdev,  0x4c, 0x2ec1);



Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
          "DMA used to run at 180 Mb/s. With the new hardware it's only
           30 Mb/s. Must be a software problem......." -actual complaint.
            Note 96.31% of all statistics are fiction.



             reply	other threads:[~2004-08-30 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 14:02 Richard B. Johnson [this message]
2004-08-30 13:15 ` Alan Cox
2004-08-30 15:04   ` Arthur Perry
2004-08-30 15:34     ` Arthur Perry
2004-08-30 17:26       ` Richard B. Johnson
2004-08-30 17:17     ` Richard B. Johnson
2004-08-30 18:13       ` Arthur Perry
     [not found] <2yV1c-29L-7@gated-at.bofh.it>
     [not found] ` <2yVb1-2ft-57@gated-at.bofh.it>
2004-08-30 15:28   ` Andi Kleen
2004-08-30 17:20     ` Richard B. Johnson
2004-08-30 17:45       ` Andi Kleen

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=Pine.LNX.4.53.0408300955470.21607@chaos \
    --to=root@chaos.analogic.com \
    --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

all inboxes | Powered by JetHome®