public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@dds.nl>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.4.9-ac17 Adaptec AIC7XXX problems (new driver, old one works fine) (solved)
Date: Sun, 30 Sep 2001 08:57:31 +0200	[thread overview]
Message-ID: <20010930085730.G9327@humilis> (raw)
In-Reply-To: <20010929162224.E9327@humilis> <200109300011.f8U0BGY58130@aslan.scsiguy.com>
In-Reply-To: <200109300011.f8U0BGY58130@aslan.scsiguy.com>

Hi Justin,

> >The new driver for the Adaptec 7892B gives me the following problems
> >(see dmesg) on a asus a7v mobo with kernel 2.4.9-ac17.
> >
> >I have to run the system underclocked to make it boot at all. As soon
> >as I run it at 1000 or 1200 MHz, it does a Kernel panic: for safety
> >during the scsi boot part. It is a 1200MHz processor. The system runs
> >fine after the (long) boot.
> 
> IIRC, the a7v is an AMD processor with VIA chipset. If you go into the
> MB BIOS and disable all of the "Make my PCI bus go as fast as possible
> even if this means violating the spec" options, the "new" aic7xxx
> driver should work fine. I wish VIA would get a clue.

It is indeed an AMD system with the VIA KT133 chipset.

I played with the bios settings to find out with which option it would
or would not give trouble. Under Advanced, CHIP Configuration the option
Byte Merge has to be disabled to make the kernel boot fine with the new
aic7xxx driver. This is with kernel 2.4.9-ac18

The bios manual says:
Byte Merge [Enabled by default]
To optimize the data transfer on PCI, this merges a sequence of
individual memory writes (bytes or words) into a single 32-bit block of
data. However, byte merging may only be done when the bytes within a
data phase are in a prefetchable address range. Configuration options:
[Disabled] [Enabled]

Why does the old driver boot fine with this enabled, and has the new
driver troubles booting then? The system seemed to run fine after the
long boot with the new driver and byte merge enabled, so it seemes that
only the boot gives troubles. The system didn't always boot till the end
with the new kernel and byte merge enabled btw, as it sometimes stopped
with the message: Kernel panic: for safety

Anyway, thank you for the hint! It all works fine now. :-)

	Ookhoi

  reply	other threads:[~2001-09-30  6:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-29 14:22 2.4.9-ac17 Adaptec AIC7XXX problems (new driver, old one works fine) Ookhoi
2001-09-29 14:43 ` arjan
2001-09-29 15:33   ` Ookhoi
2001-09-30  0:12   ` Justin T. Gibbs
2001-09-30  0:11 ` Justin T. Gibbs
2001-09-30  6:57   ` Ookhoi [this message]
2001-09-30  7:03     ` 2.4.9-ac17 Adaptec AIC7XXX problems (new driver, old one works fine) (solved) Matthew Dharm
2001-09-30 10:21       ` Gérard Roudier
2001-09-30 16:15       ` Justin T. Gibbs
2001-09-30 16:13     ` Justin T. Gibbs
2001-09-30 16:35       ` Justin T. Gibbs

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=20010930085730.G9327@humilis \
    --to=ookhoi@dds.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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