From: Tony Vroon <tony@vroon.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: aic7xxx regression occuring after 2.6.12 final
Date: Sat, 02 Jul 2005 20:15:14 +0100 [thread overview]
Message-ID: <1120331714.22021.5.camel@localhost> (raw)
In-Reply-To: <1120331026.22021.2.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]
On Sat, 2005-07-02 at 20:03 +0100, Tony Vroon wrote:
> Output follows:
It got mangled somehow. Not sure what happened but it's corrupted near
the end. Reposting:
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 29160 Ultra160 SCSI adapter>
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
scsi0: Slave Alloc 0
(scsi0:A:0:0): Sending WDTR 0
(scsi0:A:0:0): Received WDTR 0 filtered to 0
target0:0:0: FAST-5 SCSI 1.0 MB/s ST (1020 ns, offset 255)
scsi0: target 0 using 8bit transfers
(scsi0:A:0:0): Sending SDTR period 45, offset 0
(scsi0:A:0:0): Received SDTR period 45, offset 0
Filtered to period 0, offset 0
target0:0:0: asynchronous.
scsi0: target 0 using asynchronous transfers
Vendor: FUJITSU Model: MAP3367NP Rev: 0106
Type: Direct-Access ANSI SCSI revision: 03
scsi0: Slave Configure 0
target0:0:0: asynchronous.
scsi0:A:0:0:0: Tagged Queuing enabled. Depth 32
target0:0:0: Beginning Domain Validation
(scsi0:A:0:0): Sending WDTR 1
(scsi0:A:0:0): Received WDTR 1 filtered to 1
target0:0:0: FAST-5 WIDE SCSI 2.0 MB/s ST (1020 ns, offset 255)
scsi0: target 0 using 16bit transfers
(scsi0:A:0:0): Sending SDTR period 45, offset 0
(scsi0:A:0:0): Received SDTR period 45, offset 0
Filtered to period 0, offset 0
target0:0:0: wide asynchronous
csi0: target 0 using asynchronous transfers
(scsi0:A:0:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options
7
(scsi0:A:0:0): Received PPR bus_width 1, period 9, offset 7f,
ppr_options 7
Filtered to width 1, period 9, offset 7f, options 7
target0:0:0: FAST-80 WIDE SCSI 160.0 MB/s ST IU (12.5ns, offset 127)
scsi0: target 0 synchronous at 80.0MHz DT, offset = 0x7
(scsi0:A:0:0): Unexpected busfree in Message-in phase
SEQADDR == 0x16b
target0:0:0: Write Buffer failure 70000
target0:0:0: Domain Validation Disabling Information Units
(scsi0:A:0:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options
6
(scsi0:A:0:0): refuses tagged comands. Performing non-tagged I/O
target0:0:0: FAST-80 WIDE SCSI 160.0 MB/s ST IU (12.5 ns, offset 127)
*PC hangs here*
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2005-07-02 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 22:50 aic7xxx regression occuring after 2.6.12 final Tony Vroon
2005-07-02 15:42 ` Tony Vroon
2005-07-02 16:22 ` James Bottomley
2005-07-02 16:46 ` Tony Vroon
2005-07-02 17:01 ` James Bottomley
2005-07-02 17:13 ` Tony Vroon
2005-07-02 17:33 ` James Bottomley
2005-07-02 17:47 ` Tony Vroon
2005-07-02 18:36 ` James Bottomley
2005-07-02 19:03 ` Tony Vroon
2005-07-02 19:15 ` Tony Vroon [this message]
2005-07-02 19:46 ` James Bottomley
2005-07-02 20:04 ` Tony Vroon
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=1120331714.22021.5.camel@localhost \
--to=tony@vroon.org \
--cc=James.Bottomley@SteelEye.com \
--cc=apw@shadowen.org \
--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;
as well as URLs for NNTP newsgroup(s).