From: Nick Papadonis <nick@coelacanth.com>
To: linux-kernel@vger.kernel.org
Cc: gibbs@scsiguy.com
Subject: Re: AIC7XXX + v2.4.18 problems?
Date: Wed, 19 Jun 2002 11:15:10 -0400 [thread overview]
Message-ID: <m3fzzj2tc1.fsf@noop.bombay> (raw)
In-Reply-To: <m3k7ov2tly.fsf@noop.bombay> (Nick Papadonis's message of "Wed, 19 Jun 2002 11:09:13 -0400")
I wonder if problems are due to my VIA PCI chipset? Here are some details:
Bus 0, device 10, function 0:
SCSI storage controller: Adaptec AIC-7892A U160/m (rev 2).
IRQ 12.
Master Capable. Latency=32. Min Gnt=40.Max Lat=25.
I/O at 0xa800 [0xa8ff].
Non-prefetchable 64 bit memory at 0xdf000000 [0xdf000fff].
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 196).
Prefetchable 32 bit memory at 0xe7000000 [0xe7ffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (rev 0).
Master Capable. No bursts. Min Gnt=8.
Nick Papadonis <nick@coelacanth.com> writes:
> Is anyone else having problems with the AIC7XXX driver using a AHA-29160
> controller? I believe my kernel is going into a unrecoverable spin-lock
> when there is high SCSI load. I'm assuming this because the keyboard
> lights still function and network still replies to pings.
>
> In addition the 'st' driver returns with unrecoverable errors when
> trying to tar to tape. This usually occurs after a few hundred
> megabytes have been pushed through a device.
>
> My setup is :
> - AHA-29160N controller
> - Internal 50 PIN / SCSI-2 port in use
> - See below for connected drives
>
> I tested the following kernels and they display similar behavior:
> - v2.4.9
> - v2.4.18
> - v2.4.18 with updated 7XXX driver
> - v2.4.19-pre10
>
> Any insight is appreciated.
>
> - Nick
next prev parent reply other threads:[~2002-06-19 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 15:09 AIC7XXX + v2.4.18 problems? Nick Papadonis
2002-06-19 15:15 ` Nick Papadonis [this message]
2002-06-19 15:35 ` Doug Ledford
2002-06-19 21:49 ` J.A. Magallon
2002-06-20 19:16 ` Doug Ledford
2002-06-20 22:31 ` J.A. Magallon
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=m3fzzj2tc1.fsf@noop.bombay \
--to=nick@coelacanth.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.