mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@witbe.net>
To: "'Justin T. Gibbs'" <gibbs@scsiguy.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.54] Oops IDE-SCSI and failure AIC7xxx
Date: Sun, 5 Jan 2003 20:57:32 +0100	[thread overview]
Message-ID: <013901c2b4f4$af8c42a0$2101a8c0@witbe> (raw)
In-Reply-To: <452090000.1041785566@aslan.scsiguy.com>

Hello,

> There may be options in your BIOS to disable this "feature".  
> Look for things like "PCI byte-merging" and/or "PCI read 
> prefetch".  I haven't had access to one of the new SIS based 
> P4 systems yet, so I don't know how they are setup or exactly 
> how they are violating the PCI spec.  The test will fail 
> either if byte-merging or read prefetch occurs and perhaps if 
> there is an MTTR covering the memory mapped region of the 
> chip that is set to write combining mode (I don't think that 
> the mb() we issue after every memory write helps in this last case).

I've been looking at the PCI option in the BIOS...

1st part is mapping IRQ to PCI slots...
Then, you have :
PCI/VGA Palette Snoop         Disabled
PCI Latency Timer             32
Primary VGA BIOS              PCI VGA Card
USB Function                  Enabled
USB2.0 Function               Enabled
Onboard LAN Boot ROM          Disabled

Maybe related, the memory config :
SDRAM Configuration           By SPD
Chipset clock mode            Synchronous
SDRam Command Lead-off time   Auto
Graphics Aperture Size        256 MB
AGP Capability                4x Mode
AGP Fast Write Capability     Enabled
Video Memory Cache Mode       UC
Memory hole at 15M-16M        Disabled
PCI 2.1 Support               Enabled
Onboard PCI IDE Enable        Both
IDE Bus Master Support        Enabled

Could it be PCI 2.1 Support ? Don't think because I've restarted
with it disabled, and I still have the same problem...

Regards,
Paul


  reply	other threads:[~2003-01-05 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 11:01 Paul Rolland
2003-01-05 15:50 ` Justin T. Gibbs
2003-01-05 15:55   ` Paul Rolland
2003-01-05 16:52     ` Justin T. Gibbs
2003-01-05 19:57       ` Paul Rolland [this message]
2003-01-05 20:19         ` Justin T. Gibbs
2003-01-06  0:31           ` J.A. Magallon
2003-01-06  2:43   ` David Lang
2003-01-06  3:08     ` Justin T. Gibbs
2003-01-06  2:59       ` David Lang
2003-01-06  3:29         ` Justin T. Gibbs
2003-01-06  4:36           ` David Lang
2003-01-06  5:00             ` Justin T. Gibbs
2003-01-06  5:13               ` David Lang
2003-01-06 16:18                 ` Justin T. Gibbs
2003-01-06 21:00   ` Ion Badulescu

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='013901c2b4f4$af8c42a0$2101a8c0@witbe' \
    --to=rol@witbe.net \
    --cc=gibbs@scsiguy.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

Powered by JetHome