From: Mike Anderson <andmike@us.ibm.com>
To: Olaf Hering <olh@suse.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
willy@debian.org, SCSI Mailing List <linux-scsi@vger.kernel.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] fix sym2 negotiation
Date: Tue, 24 Aug 2004 13:39:14 -0700 [thread overview]
Message-ID: <20040824203914.GA25755@us.ibm.com> (raw)
In-Reply-To: <20040824132936.GA25263@suse.de>
Olaf Hering [olh@suse.de] wrote:
> On Sat, Aug 21, James Bottomley wrote:
>
> > The problems with domain validation were just the tip of the iceberg in
> > the sym2 driver. Most of its problems seem to come from an overly
> > complex set of negotiating rules, which I've swept away with this patch.
>
> I see timeouts on the CDROM during boot with 2.6.8, they do not happen
> with our 2.6.5 based SLES9 kernel. This patch doesnt fix it, no idea if
> it was supposed to fix this sort of error.
>
> PCI: Enabling device: (0003:61:01.0), cmd 143
> sym1: <875> rev 0x3 at pci 0003:61:01.0 irq 86
> sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym1: SCSI BUS has been reset.
> scsi1 : sym-2.1.18j
> sym1:5:0: ABORT operation started.
> sym1:5:0: ABORT operation timed-out.
> sym1:5:0: DEVICE RESET operation started.
> sym1:5:0: DEVICE RESET operation complete.
> sym1:5:control msgout: c.
> sym1: TARGET 5 has been reset.
> sym1:5:0: ABORT operation started.
> sym1:5:0: ABORT operation complete.
> sym1:5:0: BUS RESET operation started.
> sym1:5:0: BUS RESET operation complete.
> sym1: SCSI BUS reset detected.
> sym1: SCSI BUS has been reset.
> Vendor: IBM Model: DROM00203 Rev: 7R41
> Type: CD-ROM ANSI SCSI revision: 02
> scsi(1:0:5:0): Beginning Domain Validation
> sym1:5: wide asynchronous.
> sym1:5: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 14)
> scsi(1:0:5:0): Domain Validation skipping write tests
> scsi(1:0:5:0): Ending Domain Validation
> sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> Attached scsi CD-ROM sr0 at scsi1, channel 0, id 5, lun 0
I would guess this cdrom is behind a ACARD. We have had issues in
the past with negotiation / interaction between the ACARD and the sym.
I currently do not have local access to a system with this config, but I
am asking around to see if I can get access to one.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2004-08-24 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 18:37 [PATCH] fix sym2 negotiation James Bottomley
2004-08-22 17:32 ` Matthias Andree
2004-08-22 18:03 ` James Bottomley
2004-08-24 13:29 ` Olaf Hering
2004-08-24 20:39 ` Mike Anderson [this message]
2004-08-24 20:48 ` Vladimir G. Ivanovic
2004-08-24 20:50 ` Matthew Wilcox
2004-08-24 21:39 ` Vladimir G. Ivanovic
2004-08-24 22:12 ` Matthew Wilcox
2004-08-25 0:48 ` Vladimir G. Ivanovic
2004-08-24 20:51 ` Olaf Hering
2004-08-25 6:57 ` Mike Anderson
2004-08-25 9:25 ` Olaf Hering
2004-08-25 11:58 ` Matthew Wilcox
2004-08-25 12:09 ` Olaf Hering
2004-08-25 12:11 ` Anton Blanchard
2004-08-25 13:43 ` Doug Maxey
2004-08-25 13:23 ` James Bottomley
2004-08-25 19:13 ` Mike Anderson
2004-08-27 16:54 ` Kai Makisara
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=20040824203914.GA25755@us.ibm.com \
--to=andmike@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=anton@samba.org \
--cc=linux-scsi@vger.kernel.org \
--cc=olh@suse.de \
--cc=willy@debian.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