public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kevin@sylandro.com
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze
Date: Mon, 16 Dec 2002 08:52:03 +1100	[thread overview]
Message-ID: <20021215215203.GA29455@guarana.org> (raw)
In-Reply-To: <17460000.1039982505@aslan.btc.adaptec.com>

On Sun, Dec 15, 2002 at 01:01:45PM -0700, Justin T. Gibbs wrote:
> > On Fri, 13 Dec 2002 11:51:27 +1100, 
> > Kevin Easton <kevin@sylandro.com> wrote:
> >> I'm not sure exactly where this problem fits in, but I'm getting a 
> >> completely repeatable freeze (100% lockup, no response to keyboard)
> >> triggered by writing to /dev/st0 (dd if=/dev/urandom of=/dev/st0 bs=512
> >> count=163840 will reproduce it).
> >> So... does anyone have any ideas how I should start trying to track this
> >> down?
> 
> You might also look into your BIOS to ensure that the option "PCI Byte
> Merging" is disabled.  This option allows the chipset to perform illegal
> byte merging on the PCI bus that will upset the Adaptec.  Since the byte
> merging will only occur in certain scenarios (heavily dependent on what
> is going on with the SCSI bus), you may only see the lockup when accessing
> a particular device or running a certain program.
> 
> The latest versions of the aic7xxx and aic79xx drivers will automatically
> detect this broken VIA behavior and will fall back to using PIO for register
> access.  Although I haven't generated patches against 2.4.20, you can pull
> down a src tarball for 2.4.X that should just drop in:

OK, will do - thanks.  I don't think the BIOS on this board has such an
option, so I might have to put up with PIO register access.

	- Kevin.


  reply	other threads:[~2002-12-15 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  0:51 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze Kevin Easton
2002-12-15 11:42 ` Keith Owens
2002-12-15 12:49   ` caf
2002-12-15 20:01   ` Justin T. Gibbs
2002-12-15 21:52     ` kevin [this message]
2002-12-16  5:04     ` Kevin Easton
2002-12-16  3:52   ` caf
2002-12-16  4:47     ` Keith Owens
2002-12-16  5:21       ` Kevin Easton

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=20021215215203.GA29455@guarana.org \
    --to=kevin@sylandro.com \
    --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