All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Delete trailing full stop
Date: Fri, 18 Nov 2005 16:42:10 +1000	[thread overview]
Message-ID: <437D77C2.3000908@torque.net> (raw)
In-Reply-To: <20051117181343.GD17171@parisc-linux.org>

Matthew Wilcox wrote:
> None of the other domain validation messages have a trailing full stop,
> so I don't see why this one should.

Speaking of domain validation messages I have noticed
that either the sym53c8xx driver or scsi_transport_spi is
getting noisier in this area.

After "hot plugging" a U160 disk on a unpopulated bus
and then scanning the bus there was lots of redundant
noise on my console and log. The disk had autospin off
so a START STOP UNIT command was needed followed by a wait
for the disk to spin up. This is what I saw in my log after:
  # echo 1 > /sys/class/scsi_host/host0/scan

  Vendor: FUJITSU   Model: MAM3184MP         Rev: 0106
  Type:   Direct-Access                      ANSI SCSI revision: 03
 target0:0:3: tagged command queuing enabled, command queue depth 16.
 target0:0:3: Beginning Domain Validation
 target0:0:3: asynchronous.
 target0:0:3: wide asynchronous.
 target0:0:3: Domain Validation skipping write tests
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: Ending Domain Validation
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 2 times
sdb: Spinning up disk....<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.<6> target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 target0:0:3: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
 last message repeated 7 times
.ready
SCSI device sdb: 35885344 512-byte hdwr sectors (18373 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 35885344 512-byte hdwr sectors (18373 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 >
sd 0:0:3:0: Attached scsi disk sdb



Surely one "FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)"
message is sufficient?


The READ CAPACITY/fetching the caching mode page sequence
seems to be occurring twice. I also see this with scsi_debug
so it isn't a spi or lldd problem.

Doug Gilbert

  reply	other threads:[~2005-11-18  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 18:13 [PATCH] Delete trailing full stop Matthew Wilcox
2005-11-18  6:42 ` Douglas Gilbert [this message]
2005-11-18 13:20   ` Matthew Wilcox
2005-11-19  0:48     ` Douglas Gilbert

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=437D77C2.3000908@torque.net \
    --to=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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.