From: Tomas Szepe <szepe@pinerecords.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: dipankar@in.ibm.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: aic7xxx broken in 2.5.53/54 ?
Date: Wed, 8 Jan 2003 03:41:07 +0100 [thread overview]
Message-ID: <20030108024107.GA1127@louise.pinerecords.com> (raw)
In-Reply-To: <274040000.1041869813@aslan.scsiguy.com>
> [gibbs@scsiguy.com]
>
> These reads are actually more expensive than just using PIO. Neither of
> these older drivers included a test to try and catch fishy behavior.
Justin, are you quite sure that these tests actually work?
I too have just run into
aic7xxx: PCI Device 0:16:0 failed memory mapped test. Using PIO.
aic7xxx: PCI Device 0:17:0 failed memory mapped test. Using PIO.
with aic79xx-linux-2.4-20021230 (6.2.25) in Linux 2.4.21-pre3.
What makes me scratch my head in particular is:
o The chipset is i440BX aka the Compatibility King.
o I've never had *any* problems with 6.2.8.
Full ahc boot-up messages follow:
PCI: Found IRQ 11 for device 00:10.0
aic7xxx: PCI Device 0:16:0 failed memory mapped test. Using PIO.
PCI: Found IRQ 10 for device 00:11.0
aic7xxx: PCI Device 0:17:0 failed memory mapped test. Using PIO.
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.25
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.25
<Adaptec 2940 Ultra SCSI adapter>
aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs
(scsi1:A:4): 20.000MB/s transfers (20.000MHz, offset 15)
(scsi0:A:3): 20.000MB/s transfers (20.000MHz, offset 15)
Vendor: SEAGATE Model: ST39173N Rev: 6244
Type: Direct-Access ANSI SCSI revision: 02
scsi0:A:3:0: Tagged Queuing enabled. Depth 253
Vendor: SEAGATE Model: ST39173N Rev: 6244
Type: Direct-Access ANSI SCSI revision: 02
scsi1:A:4:0: Tagged Queuing enabled. Depth 253
Attached scsi disk sda at scsi0, channel 0, id 3, lun 0
Attached scsi disk sdb at scsi1, channel 0, id 4, lun 0
...
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-08 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 10:16 aic7xxx broken in 2.5.53/54 ? Dipankar Sarma
2003-01-03 15:14 ` Justin T. Gibbs
2003-01-06 7:32 ` Dipankar Sarma
2003-01-06 16:16 ` Justin T. Gibbs
2003-01-06 16:36 ` uaca
2003-01-07 11:36 ` uaca
2003-01-08 2:41 ` Tomas Szepe [this message]
2003-01-08 4:23 ` Justin T. Gibbs
2003-01-08 10:05 ` Tomas Szepe
2003-01-08 15:39 ` uaca
2003-01-09 11:52 ` David Lang
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=20030108024107.GA1127@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=dipankar@in.ibm.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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