From: James Bottomley <James.Bottomley@SteelEye.com>
To: John Stoffel <john@stoffel.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Linux-2.6.13-rc6: aic7xxx testers please..
Date: Tue, 09 Aug 2005 19:50:10 -0500 [thread overview]
Message-ID: <1123635010.5170.75.camel@mulgrave> (raw)
In-Reply-To: <17145.3629.933024.963438@smtp.charter.net>
On Tue, 2005-08-09 at 16:12 -0400, John Stoffel wrote:
> Thank you for looking into this with me, I really appreciate it. I'm
> kinda stumped why this suddenly started happening, but it could be
> hardware related of course...
Well ... there's something going on that your posted dmesg's don't seem
to cover. This:
> Vendor: SUN Model: DLT7000 Rev: 1E48
> Type: Sequential-Access ANSI SCSI revision: 02
> target1:0:6: asynchronous.
> target1:0:6: Beginning Domain Validation
> target1:0:6: wide asynchronous.
> target1:0:6: Domain Validation skipping write tests
> target1:0:6: FAST-10 WIDE SCSI 20.0 MB/s ST (100 ns, offset 8)
> target1:0:6: Ending Domain Validation
Say everything went OK with DV and the drive attaches wide and at 10MHz.
But in your previous posting, the aic proc routines said this:
> Target 6 Negotiation Settings
> User: 40.000MB/s transfers (20.000MHz, offset 127, 16bit)
> Goal: 20.000MB/s transfers (10.000MHz, offset 8, 16bit)
> Curr: 3.300MB/s transfers
> Channel A Target 6 Lun 0 Settings
> Commands Queued 1065
> Commands Active 0
> Command Openings 1
> Max Tagged Openings 0
> Device Queue Frozen Count 0
Which is the AIC driver's way of saying narrow async.
So something must have happened during the 1065 I/Os to cause this.
Hopefully that something left a trace in the logs.
James
next prev parent reply other threads:[~2005-08-10 0:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 18:47 Linux-2.6.13-rc6: aic7xxx testers please Linus Torvalds
2005-08-07 20:23 ` Heikki Orsila
2005-08-07 20:38 ` Lee Revell
2005-08-07 20:50 ` Linus Torvalds
2005-08-07 20:52 ` Lee Revell
2005-08-07 21:14 ` Dumitru Ciobarcianu
2005-08-08 14:17 ` Theodore Ts'o
2005-08-07 22:12 ` [2.6 patch] fix drivers/s390/net/ compilation Adrian Bunk
2005-08-08 8:31 ` Martin Schwidefsky
2005-08-08 12:59 ` Linux-2.6.13-rc6: aic7xxx testers please John Stoffel
2005-08-08 15:08 ` Danny ter Haar
2005-08-08 17:54 ` Jesper Juhl
2005-08-09 19:35 ` John Stoffel
2005-08-09 19:58 ` James Bottomley
2005-08-09 20:12 ` John Stoffel
2005-08-10 0:50 ` James Bottomley [this message]
2005-08-10 15:28 ` John Stoffel
2005-08-10 15:46 ` James Bottomley
2005-08-10 16:27 ` John Stoffel
2005-08-11 2:30 ` John Stoffel
2005-08-11 6:34 ` Philipp Matthias Hahn
2005-08-11 6:42 ` Philipp Matthias Hahn
2005-08-11 9:54 ` Johannes Stezenbach
2005-08-11 12:37 ` hunold
2005-08-11 14:51 ` Gene Heskett
2005-08-11 15:38 ` cx88 teletext not yet implemented -was- " Michael Krufky
2005-08-11 21:53 ` Gene Heskett
2005-08-11 15:30 ` Philipp Matthias Hahn
[not found] ` <20050815071723.GB8524@titan.lahn.de>
[not found] ` <20050815215855.GB5860@linuxtv.org>
[not found] ` <E1E4vSG-0005r7-KG@allen.werkleitz.de>
2005-08-24 6:59 ` [PATCH] saa7146_i2c device model integration Philipp Matthias Hahn
2005-08-31 12:14 ` Johannes Stezenbach
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=1123635010.5170.75.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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