linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: "ata73" == "sd 72" ?
Date: Thu, 17 Apr 2008 20:30:12 -0400	[thread overview]
Message-ID: <4807EB94.80104@rtr.ca> (raw)

While working on sata_mv today, I noticed something weird in the syslog.
The messages from libata show "ata73" for the port with my drives (pmp),
but the messages from SCSI (sd) show "sd 72" for those same drives.

One would really think that these two numbers should agree,
not be off by one.  I wonder why they differ (or why they are
almost the same) ?

   ata73.00: ATA-7: ST3400832AS, 3.03, max UDMA/133
   ata73.00: 781422768 sectors, multi 0: LBA48 NCQ (depth 31/32)
   ata73.00: configured for UDMA/133
   ata73.02: ATA-7: ST3400832AS, 3.03, max UDMA/133
   ata73.02: 781422768 sectors, multi 0: LBA48 NCQ (depth 31/32)
   ata73.02: configured for UDMA/133
   ata73: EH complete
   ata74: SATA link down (SStatus 0 SControl 300)
   ata75: SATA link down (SStatus 0 SControl 300)
   ata76: SATA link down (SStatus 0 SControl 300)
   scsi 72:0:0:0: Direct-Access     ATA      ST3400832AS      3.03 PQ: 0 ANSI: 5
   sd 72:0:0:0: [sdb] 781422768 512-byte hardware sectors (400088 MB)
   sd 72:0:0:0: [sdb] Write Protect is off
   sd 72:0:0:0: [sdb] Mode Sense: 00 3a 00 00
   sd 72:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
   sd 72:0:0:0: [sdb] 781422768 512-byte hardware sectors (400088 MB)
   sd 72:0:0:0: [sdb] Write Protect is off
   sd 72:0:0:0: [sdb] Mode Sense: 00 3a 00 00
   sd 72:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sdb: sdb1
   sd 72:0:0:0: [sdb] Attached SCSI disk
   sd 72:0:0:0: Attached scsi generic sg2 type 0
   scsi 72:2:0:0: Direct-Access     ATA      ST3400832AS      3.03 PQ: 0 ANSI: 5
   sd 72:2:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
   sd 72:2:0:0: [sdc] Write Protect is off
   sd 72:2:0:0: [sdc] Mode Sense: 00 3a 00 00
   sd 72:2:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
   sd 72:2:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
   sd 72:2:0:0: [sdc] Write Protect is off
   sd 72:2:0:0: [sdc] Mode Sense: 00 3a 00 00
   sd 72:2:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA


             reply	other threads:[~2008-04-18  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18  0:30 Mark Lord [this message]
2008-04-18  6:22 ` "ata73" == "sd 72" ? Jeff Garzik
2008-04-18  8:13   ` Mikael Pettersson
2008-04-24  3:38     ` Tejun Heo

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=4807EB94.80104@rtr.ca \
    --to=liml@rtr.ca \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@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).