public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Keith Owens <kaos@ocs.com.au>, Kevin Easton <kevin@sylandro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze
Date: Sun, 15 Dec 2002 13:01:45 -0700	[thread overview]
Message-ID: <17460000.1039982505@aslan.btc.adaptec.com> (raw)
In-Reply-To: <1047.1039952560@ocs3.intra.ocs.com.au>

> 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:

http://~people.FreeBSD.org/~gibbs/linux/SRC/

--
Justin


  parent reply	other threads:[~2002-12-15 19:56 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 [this message]
2002-12-15 21:52     ` kevin
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=17460000.1039982505@aslan.btc.adaptec.com \
    --to=gibbs@scsiguy.com \
    --cc=kaos@ocs.com.au \
    --cc=kevin@sylandro.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