linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ajit Prem <Ajit.Prem@motorola.com>
To: linux-ide@vger.kernel.org
Subject: sata_vsc and gd31244 on an Intel IQ3124H card
Date: Thu, 07 Oct 2004 09:56:21 -0700	[thread overview]
Message-ID: <41657535.1070407@motorola.com> (raw)

Hello,

My SATA disk does not get recognized off
an Intel IQ3124H PCI card that uses the gd31244.
I'm using standard 2.6.8.1 on an MPC8540ADS
board. The IQ3124H card has 4 ports. I connected
the first port to a Maxtor Maxline Plus SATA disk.
I turned on debugging for libata and got the
following messages:


sata_vsc version 0.01
ata_device_add: ENTER
ata_host_add: ENTER
ata_port_start: prd alloc, virt c75ae000, dma 75ae000
ata1: SATA max UDMA/133 cmd 0xCA05F200 ctl 0xCA05F229 bmdma 0xCA05F270 
irq 100
ata_host_add: ENTER
ata_port_start: prd alloc, virt c7029000, dma 7029000
ata2: SATA max UDMA/133 cmd 0xCA05F400 ctl 0xCA05F429 bmdma 0xCA05F470 
irq 100
ata_host_add: ENTER
ata_port_start: prd alloc, virt c702a000, dma 702a000
ata3: SATA max UDMA/133 cmd 0xCA05F600 ctl 0xCA05F629 bmdma 0xCA05F670 
irq 100
kernel: ata_host_add: ENTER
ata_port_start: prd alloc, virt c702c000, dma 702c000
ata4: SATA max UDMA/133 cmd 0xCA05F800 ctl 0xCA05F829 bmdma 0xCA05F870 
irq 100
ata_device_add: probe begin
ata_device_add: ata1: probe begin
ata1: no device found (phy stat 00e050c0)
ata_device_add: ata1: probe end
scsi0 : sata_vsc
ata_device_add: ata2: probe begin
ata2: no device found (phy stat 00008038)
ata_device_add: ata2: probe end
scsi1 : sata_vsc
ata_device_add: ata3: probe begin
ata3: no device found (phy stat 00008038)
ata_device_add: ata3: probe end
scsi2 : sata_vsc
ata_device_add: ata4: probe begin
ata4: no device found (phy stat 2a006d71)
ata_device_add: ata4: probe end
scsi3 : sata_vsc
ata_device_add: probe begin
ata_scsi_dump_cdb: CDB (1:0,0,0) 12 00 00 00 24 00 00 00 00
ata_scsi_dump_cdb: CDB (1:0,1,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,2,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,3,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,4,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,5,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,6,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,7,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,8,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,9,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,10,0) 12 00 00 00 2400 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,11,0) 12 00 00 00 2400 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,12,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,13,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,14,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:0,15,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,0,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,1,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,2,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,3,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,4,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,5,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,6,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,7,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,8,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,9,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,10,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,11,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,12,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,13,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,14,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (1:1,15,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,0,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,1,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,2,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,3,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,4,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,5,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,6,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,7,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,8,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (2:0,9,0) 12 00 00 00 24 00 58 00 c7
...
and so on, till
ata_scsi_dump_cdb: CDB (4:1,14,0) 12 00 00 00 24 00 58 00 c7
ata_scsi_dump_cdb: CDB (4:1,15,0) 12 00 00 00 24 00 58 00 c7
sata_vsc after device add


sata_vsc has been built as a module. If I unload and reload
the module, the phy_stat values in the log above change to
something else.

Any advise on what I should do to be able to use my SATA disk?

Thanks,

AP


                 reply	other threads:[~2004-10-07 16:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41657535.1070407@motorola.com \
    --to=ajit.prem@motorola.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).