Hi Alan,
thanks a lot. Disabling all the ATA/ATAPI stuff in the kernel helped. The
system is reacting better when accessing a dvd.
My optical drive is named /dev/sr0 now. hdparm shows slow performance, with
the old config it shows a much better performance. But the reality is
different. Now
ata_wait_idle() complains when the device isn't idle 10ms wait.
However, this function sometimes is used on empty ports. As SATA
controllers report arbitrary status on empty ports, this causes
spurious warning messages.
* separate ata_wait_idle_quiet() from ata_wait_idle()
* use _quiet version
Hello,
Sigmund Scheinbar wrote:
The following messages appear while booting/in dmesg [1]:
[...]
ata2: port is slow to respond, please be patient (Status 0x80)
ata2: port failed to respond (30 secs, Status 0x80)
ata2: softreset failed (device not ready)
ata2: softreset failed, retrying in
Mike Accetta wrote:
The version of hdparm on this box gives
dev/sdb:
operation not supported on SCSI disks
against the SCSI disk name. With the controller in compatible mode,
here is the 'hdparm -I /dev/hdb' output on the same disk:
ATA device, with non-removable media
Tejun Heo wrote:
James Ray wrote:
Jeff, All,
We have just started using some new machines with The Intel ESB2
chipset in them (PCI Id: 8086:2681) for the SATA Controller.
With any kernels above 2.6.15 (as far as I can tell from my testing at
least) we are getting problems with them.
Tejun Heo writes:
Mike Accetta wrote:
The version of hdparm on this box gives
dev/sdb:
operation not supported on SCSI disks
against the SCSI disk name. With the controller in compatible mode,
here is the 'hdparm -I /dev/hdb' output on the same disk:
ATA device, with
Hi Jeff,
I'd be very grateful to get your advice on the following issue:
My Promise Sata150 SX4 adapter doesn't work with the sata_sx4 driver
versions 0.7, 0.8 and 0.9. The card is properly shown by lspci:
:04:02.0 RAID bus controller: Promise Technology, Inc. PDC20621
[SATA150 SX4] 4
The driver used to merge the address setup timing for the secondary channel but
this must have been done for both channels actually despite the primary channel
had separate registers for each drive (I'afraid that this is too common mistake
in both hardware and software -- address setup timing must
There have been some reports of intermittent errors
with sata_promise, especially with newer disks.
My theory is that the driver isn't initialisating the
controller properly for SATAII 3Gbps transfer speeds.
It would be helpful if people seeing intermittent errors
with sata_promise could do the
Mikael Pettersson wrote:
+ if (hp-flags PDC_FLAG_GEN_II) {
+ /* record ASIC rev */
+ pci_read_config_byte(pdev, PCI_REVISION_ID, hp-asic_rev);
+
+#if 1
+ /* set cache line size = 1 */
+ pci_read_config_byte(pdev, PCI_CACHE_LINE_SIZE,
Eric == Moore, Eric [EMAIL PROTECTED] writes:
Eric Martin K. Petersen on Data Intergrity Feature, which is also
Eric called EEDP(End to End Data Protection), which he presented some
Eric ideas/suggestions of adding an API in linux for this.
T10 DIF is interesting for a few things:
-
These features make the most sense in terms of WRITE. Disks already
have plenty of CRC on the data so if a READ fails on a regular drive
we already know about it.
Don't bet on it. If you want to do this seriously you need an end to end
(media to host ram) checksum. We do see bizarre and quite
On Feb 27, 2007 19:02 +, Alan wrote:
It would be great if the app tag was more than 16 bits. Ted mentioned
that ideally he'd like to store the inode number in the app tag. But
as it stands there isn't room.
The lowest few bits are the most important with ext2/ext3 because you
Martin K. Petersen wrote:
Eric == Moore, Eric [EMAIL PROTECTED] writes:
Eric Martin K. Petersen on Data Intergrity Feature, which is also
Eric called EEDP(End to End Data Protection), which he presented some
Eric ideas/suggestions of adding an API in linux for this.
T10 DIF is interesting
Alan == Alan [EMAIL PROTECTED] writes:
These features make the most sense in terms of WRITE. Disks
already have plenty of CRC on the data so if a READ fails on a
regular drive we already know about it.
Alan Don't bet on it.
This is why I mentioned that I want to expose the protection
Alan == Alan [EMAIL PROTECTED] writes:
Not sure you're up-to-date on the T10 data integrity feature.
Essentially it's an extension of the 520 byte sectors common in
disk
[...]
Alan but here's a minor bit of passing bad news - quite a few older
Alan ATA controllers can't issue DMA transfers
Gregory Youngblood wrote:
I'm seeing several problems with a Silicon Image 3124 and Norco
DS-1220 external sata shelf with two Silicon Image 3726 port
multipliers and 8 500gb 7200.10 Seagate sata hard drives. The
hardware is known to be good. Or at least the Dell server is. The
only new
Please apply the attached patch over 2.6.20.1 and report how it works.
Thanks.
--
tejun
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index 6d93240..2d7d97d 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -80,6 +80,7 @@ enum {
board_ahci_pi = 1,
board_ahci_vt8251 = 2,
Blacklist FUJITSU MHT2060BH for NCQ. On this drive, NCQ works iff
queue depth is equal to or less than 4. Just turn it off.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
Cc: Mike Accetta [EMAIL PROTECTED]
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index bdde327..69665c8
Clearing drvdata in -remove_one causes NULL pointer deference. Clear
drvdata only in ata_host_release() after all resources are freed.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
pata_pcmcia is fixed by Alan's patch. This fixes other drivers and
make libata always clear drvdata after detach.
Hello!
As reported by John Williams and others like in
http://www.mail-archive.com/linux-ide@vger.kernel.org/msg03088.html
I too have a problem with 2.6.20.1 using ata_piix not detecting the
CD-ROM any more. Applying the patch from
http://lkml.org/lkml/2007/2/12/24 did not help, but additionally
On Fri, 2007-02-23 at 12:00 -0500, Dale Blount wrote:
Hi,
Excuse me if this has been covered or fixed, I couldn't find anything in
the archives.
I upgraded from 2.6.11.7 to 2.6.20.1 today and found all the drives
connected to 2 brands of sata_sil sata controllers not working. The
drives
On Tue, 27 Feb 2007 15:00:29 +0200 (EET)
Meelis Roos [EMAIL PROTECTED] wrote:
Subject: ata-piix ACPI errors (40/80 pin cable mix)
References : http://lkml.org/lkml/2007/2/22/159
Submitter : Meelis Roos [EMAIL PROTECTED]
Status : unknown
Still appears, but this does not seem to
Subject: ata-piix ACPI errors (40/80 pin cable mix)
References : http://lkml.org/lkml/2007/2/22/159
Submitter : Meelis Roos [EMAIL PROTECTED]
Status : unknown
Still appears, but this does not seem to be 40/80 pin cable problem to
be but rather ata-piix calling some acpi methods and
24 matches
Mail list logo
