From: Yuri Kirsanov <flash@rccb.ru>
To: linux-ide@vger.kernel.org
Cc: jgarzik@pobox.com
Subject: TX4000 RAID and sata_promise
Date: Sun, 28 Aug 2005 18:46:30 +0400 [thread overview]
Message-ID: <19927573359.20050828184630@rccb.ru> (raw)
Look's like I've found solution. I've checked libata_core.c and found
following strings in it (line 1427):
if (sata_dev_present(ap))
ata_port_probe(ap);
else {
sstatus = scr_read(ap, SCR_STATUS);
printk(KERN_INFO "ata%u: no device found (phy stat %08x)\n",
ap->id, sstatus);
ata_port_disable(ap);
}
For experiment, I made following changes:
// if (sata_dev_present(ap))
ata_port_probe(ap);
/* else {
sstatus = scr_read(ap, SCR_STATUS);
printk(KERN_INFO "ata%u: no device found (phy stat %08x)\n",
ap->id, sstatus);
ata_port_disable(ap);
}
*/
So, now it's always do port-probe, and here is the result:
libata version 1.12 loaded.
sata_promise version 1.02
PCI: Found IRQ 9 for device 0000:01:0a.0
ata1: PATA max UDMA/133 cmd 0xCC81C200 ctl 0xCC81C238 bmdma 0x0 irq 9
ata2: PATA max UDMA/133 cmd 0xCC81C280 ctl 0xCC81C2B8 bmdma 0x0 irq 9
ata3: PATA max UDMA/133 cmd 0xCC81C300 ctl 0xCC81C338 bmdma 0x0 irq 9
ata4: PATA max UDMA/133 cmd 0xCC81C380 ctl 0xCC81C3B8 bmdma 0x0 irq 9
ATA: abnormal status 0x8 on port 0xCC81C21C
ata1: disabling port
scsi0 : sata_promise
ata2: dev 0 cfg 49:0b00 82:346b 83:4208 84:4000 85:3461 86:0000 87:4000 88:101f
ata2: dev 0 ATA, max UDMA/66, 17840592 sectors:
ata2(0): applying bridge limits
ata2: dev 0 configured for UDMA/66
scsi1 : sata_promise
ATA: abnormal status 0x8 on port 0xCC81C31C
ata3: disabling port
scsi2 : sata_promise
ATA: abnormal status 0x8 on port 0xCC81C39C
ata4: disabling port
scsi3 : sata_promise
Vendor: ATA Model: FUJITSU MPF3102A Rev: 5C18
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 17840592 512-byte hdwr sectors (9134 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 17840592 512-byte hdwr sectors (9134 MB)
SCSI device sda: drive cache: write back
sda:<4>ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x84 { DriveStatusError BadCRC }
sda1
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0
As you can see, my device is found ok, I was able to format it and
mount it. Seek errors may be because of bad disk state, I'm trying to
make some checks on it. I understand, that I made really incorrect
commenting out, but maybe now somebody will be able to make this
driver work correctly with an PATA devices?
next reply other threads:[~2005-08-28 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 14:46 Yuri Kirsanov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-28 17:08 TX4000 RAID and sata_promise Yuri Kirsanov
2005-08-29 8:57 ` Erik Slagter
2005-08-28 13:33 Yuri Kirsanov
2005-08-29 8:52 ` Erik Slagter
2005-08-23 8:08 Yuri Kirsanov
2005-08-22 6:28 Allen Bolderoff
2005-08-20 8:46 Yuri Kirsanov
2005-08-16 5:30 Yuri Kirsanov
2005-08-16 13:10 ` Tyler
2005-08-16 13:30 ` Erik Slagter
2005-08-16 13:35 ` Yuri Kirsanov
2005-08-16 13:50 ` Erik Slagter
2005-08-16 13:54 ` Yuri Kirsanov
2005-06-23 17:05 Yuri Kirsanov
2005-08-18 17:11 ` Erik Slagter
2005-06-19 12:20 Yuri Kirsanov
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=19927573359.20050828184630@rccb.ru \
--to=flash@rccb.ru \
--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 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.